0s autopkgtest [04:56:59]: starting date and time: 2025-02-22 04:56:59+0000 0s autopkgtest [04:56:59]: git checkout: 325255d2 Merge branch 'pin-any-arch' into 'ubuntu/production' 0s autopkgtest [04:56:59]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.2h_vwe_h/out --timeout-copy=6000 --setup-commands /home/ubuntu/autopkgtest-cloud/worker-config-production/setup-canonical.sh --apt-pocket=proposed=src:glib2.0 --apt-upgrade libfprint --timeout-short=300 --timeout-copy=20000 --timeout-build=20000 --env=ADT_TEST_TRIGGERS=glib2.0/2.83.4-1 -- ssh -s /home/ubuntu/autopkgtest/ssh-setup/nova -- --flavor autopkgtest --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@bos03-arm64-32.secgroup --name adt-plucky-arm64-libfprint-20250222-045659-juju-7f2275-prod-proposed-migration-environment-15-b2f8f23d-4e12-4008-9c50-5e7384daa1a6 --image adt/ubuntu-plucky-arm64-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-proposed-migration -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/ 146s autopkgtest [04:59:25]: testbed dpkg architecture: arm64 146s autopkgtest [04:59:25]: testbed apt version: 2.9.30ubuntu1 147s autopkgtest [04:59:26]: @@@@@@@@@@@@@@@@@@@@ test bed setup 147s autopkgtest [04:59:26]: testbed release detected to be: None 148s autopkgtest [04:59:27]: updating testbed package index (apt update) 148s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [110 kB] 148s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease 148s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease 148s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease 148s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [508 kB] 149s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [3120 B] 149s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [80.1 kB] 149s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [13.5 kB] 149s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 Packages [122 kB] 149s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted arm64 Packages [7960 B] 149s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe arm64 Packages [451 kB] 149s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse arm64 Packages [9060 B] 149s Fetched 1305 kB in 1s (1419 kB/s) 150s Reading package lists... 150s + lsb_release --codename --short 150s + RELEASE=plucky 150s + cat 150s + [ plucky != trusty ] 150s + DEBIAN_FRONTEND=noninteractive eatmydata apt-get -y --allow-downgrades -o Dpkg::Options::=--force-confnew dist-upgrade 150s Reading package lists... 151s Building dependency tree... 151s Reading state information... 151s Calculating upgrade... 152s Calculating upgrade... 152s The following packages will be upgraded: 152s apparmor base-files cloud-init cloud-init-base gcc-14-base libapparmor1 152s libclang-cpp18 libclang1-19 libgnutls30t64 libllvm18 libllvm19 liblsof0 152s libnss3 libperl5.40 lsof motd-news-config perl perl-base perl-modules-5.40 152s ucf vim-common vim-tiny xxd 152s 23 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 152s Need to get 90.2 MB of archives. 152s After this operation, 11.3 kB of additional disk space will be used. 152s Get:1 http://ftpmaster.internal/ubuntu plucky/main arm64 motd-news-config all 13.6ubuntu1 [5168 B] 152s Get:2 http://ftpmaster.internal/ubuntu plucky/main arm64 base-files arm64 13.6ubuntu1 [75.6 kB] 153s Get:3 http://ftpmaster.internal/ubuntu plucky/main arm64 perl-modules-5.40 all 5.40.1-2 [3217 kB] 153s Get:4 http://ftpmaster.internal/ubuntu plucky/main arm64 libperl5.40 arm64 5.40.1-2 [4779 kB] 153s Get:5 http://ftpmaster.internal/ubuntu plucky/main arm64 perl arm64 5.40.1-2 [262 kB] 153s Get:6 http://ftpmaster.internal/ubuntu plucky/main arm64 perl-base arm64 5.40.1-2 [1788 kB] 153s Get:7 http://ftpmaster.internal/ubuntu plucky/main arm64 gcc-14-base arm64 14.2.0-17ubuntu3 [53.6 kB] 153s Get:8 http://ftpmaster.internal/ubuntu plucky/main arm64 libapparmor1 arm64 4.1.0~beta5-0ubuntu5 [53.7 kB] 153s Get:9 http://ftpmaster.internal/ubuntu plucky/main arm64 libgnutls30t64 arm64 3.8.9-2ubuntu2 [962 kB] 153s Get:10 http://ftpmaster.internal/ubuntu plucky/main arm64 ucf all 3.0050 [43.5 kB] 153s Get:11 http://ftpmaster.internal/ubuntu plucky/main arm64 vim-tiny arm64 2:9.1.0967-1ubuntu2 [807 kB] 153s Get:12 http://ftpmaster.internal/ubuntu plucky/main arm64 vim-common all 2:9.1.0967-1ubuntu2 [396 kB] 153s Get:13 http://ftpmaster.internal/ubuntu plucky/main arm64 xxd arm64 2:9.1.0967-1ubuntu2 [67.8 kB] 153s Get:14 http://ftpmaster.internal/ubuntu plucky/main arm64 apparmor arm64 4.1.0~beta5-0ubuntu5 [660 kB] 153s Get:15 http://ftpmaster.internal/ubuntu plucky/main arm64 lsof arm64 4.99.4+dfsg-2 [236 kB] 153s Get:16 http://ftpmaster.internal/ubuntu plucky/main arm64 liblsof0 arm64 4.99.4+dfsg-2 [54.0 kB] 153s Get:17 http://ftpmaster.internal/ubuntu plucky/main arm64 cloud-init-base all 25.1-0ubuntu1 [616 kB] 153s Get:18 http://ftpmaster.internal/ubuntu plucky/main arm64 libclang-cpp18 arm64 1:18.1.8-16build1 [13.1 MB] 154s Get:19 http://ftpmaster.internal/ubuntu plucky/main arm64 libllvm18 arm64 1:18.1.8-16build1 [26.3 MB] 155s Get:20 http://ftpmaster.internal/ubuntu plucky/main arm64 libllvm19 arm64 1:19.1.7-1ubuntu2 [27.3 MB] 156s Get:21 http://ftpmaster.internal/ubuntu plucky/main arm64 libclang1-19 arm64 1:19.1.7-1ubuntu2 [7986 kB] 156s Get:22 http://ftpmaster.internal/ubuntu plucky/main arm64 libnss3 arm64 2:3.108-1ubuntu1 [1446 kB] 156s Get:23 http://ftpmaster.internal/ubuntu plucky/main arm64 cloud-init all 25.1-0ubuntu1 [2088 B] 157s Preconfiguring packages ... 157s Fetched 90.2 MB in 4s (23.1 MB/s) 157s (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 ... 116668 files and directories currently installed.) 157s Preparing to unpack .../motd-news-config_13.6ubuntu1_all.deb ... 157s Unpacking motd-news-config (13.6ubuntu1) over (13.5ubuntu3) ... 157s Preparing to unpack .../base-files_13.6ubuntu1_arm64.deb ... 157s Unpacking base-files (13.6ubuntu1) over (13.5ubuntu3) ... 157s Setting up base-files (13.6ubuntu1) ... 157s Updating /root/.profile to current default. 158s motd-news.service is a disabled or a static unit not running, not starting it. 158s (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 ... 116668 files and directories currently installed.) 158s Preparing to unpack .../perl_5.40.1-2_arm64.deb ... 158s Unpacking perl (5.40.1-2) over (5.40.0-8) ... 158s Preparing to unpack .../perl-modules-5.40_5.40.1-2_all.deb ... 158s Unpacking perl-modules-5.40 (5.40.1-2) over (5.40.0-8) ... 159s Preparing to unpack .../libperl5.40_5.40.1-2_arm64.deb ... 159s Unpacking libperl5.40:arm64 (5.40.1-2) over (5.40.0-8) ... 159s Preparing to unpack .../perl-base_5.40.1-2_arm64.deb ... 159s Unpacking perl-base (5.40.1-2) over (5.40.0-8) ... 159s Setting up perl-base (5.40.1-2) ... 160s (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 ... 116668 files and directories currently installed.) 160s Preparing to unpack .../00-gcc-14-base_14.2.0-17ubuntu3_arm64.deb ... 160s Unpacking gcc-14-base:arm64 (14.2.0-17ubuntu3) over (14.2.0-17ubuntu1) ... 160s Preparing to unpack .../01-libapparmor1_4.1.0~beta5-0ubuntu5_arm64.deb ... 160s Unpacking libapparmor1:arm64 (4.1.0~beta5-0ubuntu5) over (4.1.0~beta5-0ubuntu4) ... 160s Preparing to unpack .../02-libgnutls30t64_3.8.9-2ubuntu2_arm64.deb ... 160s Unpacking libgnutls30t64:arm64 (3.8.9-2ubuntu2) over (3.8.9-2ubuntu1) ... 160s Preparing to unpack .../03-ucf_3.0050_all.deb ... 160s Unpacking ucf (3.0050) over (3.0049) ... 160s Preparing to unpack .../04-vim-tiny_2%3a9.1.0967-1ubuntu2_arm64.deb ... 160s Unpacking vim-tiny (2:9.1.0967-1ubuntu2) over (2:9.1.0861-1ubuntu1) ... 160s Preparing to unpack .../05-vim-common_2%3a9.1.0967-1ubuntu2_all.deb ... 160s Unpacking vim-common (2:9.1.0967-1ubuntu2) over (2:9.1.0861-1ubuntu1) ... 160s Preparing to unpack .../06-xxd_2%3a9.1.0967-1ubuntu2_arm64.deb ... 160s Unpacking xxd (2:9.1.0967-1ubuntu2) over (2:9.1.0861-1ubuntu1) ... 160s Preparing to unpack .../07-apparmor_4.1.0~beta5-0ubuntu5_arm64.deb ... 161s Unpacking apparmor (4.1.0~beta5-0ubuntu5) over (4.1.0~beta5-0ubuntu4) ... 162s Preparing to unpack .../08-lsof_4.99.4+dfsg-2_arm64.deb ... 162s Unpacking lsof (4.99.4+dfsg-2) over (4.99.4+dfsg-1) ... 162s Preparing to unpack .../09-liblsof0_4.99.4+dfsg-2_arm64.deb ... 162s Unpacking liblsof0 (4.99.4+dfsg-2) over (4.99.4+dfsg-1) ... 162s Preparing to unpack .../10-cloud-init-base_25.1-0ubuntu1_all.deb ... 162s /usr/bin/py3clean:101: DeprecationWarning: glob.glob1 is deprecated and will be removed in Python 3.15. Use glob.glob and pass a directory to its root_dir argument instead. 162s for fn in glob1(directory, "%s.*" % fname): 163s Unpacking cloud-init-base (25.1-0ubuntu1) over (25.1~3geb1965a4-0ubuntu1) ... 163s Preparing to unpack .../11-libclang-cpp18_1%3a18.1.8-16build1_arm64.deb ... 163s Unpacking libclang-cpp18 (1:18.1.8-16build1) over (1:18.1.8-15) ... 163s Preparing to unpack .../12-libllvm18_1%3a18.1.8-16build1_arm64.deb ... 163s Unpacking libllvm18:arm64 (1:18.1.8-16build1) over (1:18.1.8-15) ... 164s Preparing to unpack .../13-libllvm19_1%3a19.1.7-1ubuntu2_arm64.deb ... 164s Unpacking libllvm19:arm64 (1:19.1.7-1ubuntu2) over (1:19.1.7-1ubuntu1) ... 165s Preparing to unpack .../14-libclang1-19_1%3a19.1.7-1ubuntu2_arm64.deb ... 165s Unpacking libclang1-19 (1:19.1.7-1ubuntu2) over (1:19.1.7-1ubuntu1) ... 165s Preparing to unpack .../15-libnss3_2%3a3.108-1ubuntu1_arm64.deb ... 165s Unpacking libnss3:arm64 (2:3.108-1ubuntu1) over (2:3.107-1ubuntu1) ... 165s Preparing to unpack .../16-cloud-init_25.1-0ubuntu1_all.deb ... 165s Unpacking cloud-init (25.1-0ubuntu1) over (25.1~3geb1965a4-0ubuntu1) ... 165s Setting up libgnutls30t64:arm64 (3.8.9-2ubuntu2) ... 165s Setting up motd-news-config (13.6ubuntu1) ... 165s Setting up libllvm19:arm64 (1:19.1.7-1ubuntu2) ... 165s Setting up libapparmor1:arm64 (4.1.0~beta5-0ubuntu5) ... 165s Setting up libclang1-19 (1:19.1.7-1ubuntu2) ... 165s Setting up gcc-14-base:arm64 (14.2.0-17ubuntu3) ... 165s Setting up liblsof0 (4.99.4+dfsg-2) ... 166s Setting up libnss3:arm64 (2:3.108-1ubuntu1) ... 166s Setting up cloud-init-base (25.1-0ubuntu1) ... 168s Setting up xxd (2:9.1.0967-1ubuntu2) ... 168s Setting up apparmor (4.1.0~beta5-0ubuntu5) ... 168s Installing new version of config file /etc/apparmor.d/fusermount3 ... 169s Reloading AppArmor profiles 171s Setting up vim-common (2:9.1.0967-1ubuntu2) ... 171s Setting up ucf (3.0050) ... 171s Setting up lsof (4.99.4+dfsg-2) ... 171s Setting up perl-modules-5.40 (5.40.1-2) ... 171s Setting up libllvm18:arm64 (1:18.1.8-16build1) ... 171s Setting up cloud-init (25.1-0ubuntu1) ... 171s Setting up vim-tiny (2:9.1.0967-1ubuntu2) ... 171s Setting up libperl5.40:arm64 (5.40.1-2) ... 171s Setting up perl (5.40.1-2) ... 171s Setting up libclang-cpp18 (1:18.1.8-16build1) ... 171s Processing triggers for rsyslog (8.2412.0-2ubuntu1) ... 171s Processing triggers for systemd (257.2-3ubuntu1) ... 171s Processing triggers for man-db (2.13.0-1) ... 174s Processing triggers for plymouth-theme-ubuntu-text (24.004.60-2ubuntu5) ... 174s Processing triggers for install-info (7.1.1-1) ... 174s Processing triggers for libc-bin (2.40-4ubuntu1) ... 174s Processing triggers for initramfs-tools (0.145ubuntu2) ... 174s update-initramfs: Generating /boot/initrd.img-6.12.0-15-generic 174s W: No lz4 in /usr/bin:/sbin:/bin, using gzip 199s System running in EFI mode, skipping. 199s + rm /etc/apt/preferences.d/force-downgrade-to-release.pref 199s + /usr/lib/apt/apt-helper analyze-pattern ?true 199s + uname -r 199s + sed s/\./\\./g 199s + running_kernel_pattern=^linux-.*6\.12\.0-15-generic.* 199s + apt list ?obsolete 199s + tail -n+2 199s + cut -d/ -f1 199s + grep -v ^linux-.*6\.12\.0-15-generic.* 200s + true 200s + obsolete_pkgs= 200s + DEBIAN_FRONTEND=noninteractive eatmydata apt-get -y purge --autoremove 200s Reading package lists... 200s Building dependency tree... 200s Reading state information... 201s Solving dependencies... 201s 0 upgraded, 0 newly installed, 0 to remove and 3 not upgraded. 201s + grep -q trusty /etc/lsb-release 201s + [ ! -d /usr/share/doc/unattended-upgrades ] 201s + [ ! -d /usr/share/doc/lxd ] 201s + [ ! -d /usr/share/doc/lxd-client ] 201s + [ ! -d /usr/share/doc/snapd ] 201s + type iptables 201s + cat 201s + chmod 755 /etc/rc.local 201s + . /etc/rc.local 201s + iptables -w -t mangle -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu 201s + iptables -A OUTPUT -d 10.255.255.1/32 -p tcp -j DROP 201s + iptables -A OUTPUT -d 10.255.255.2/32 -p tcp -j DROP 201s + uname -m 201s + [ aarch64 = ppc64le ] 201s + [ -d /run/systemd/system ] 201s + systemd-detect-virt --quiet --vm 201s + mkdir -p /etc/systemd/system/systemd-random-seed.service.d/ 201s + cat 201s + grep -q lz4 /etc/initramfs-tools/initramfs.conf 201s + echo COMPRESS=lz4 201s autopkgtest [05:00:20]: upgrading testbed (apt dist-upgrade and autopurge) 202s Reading package lists... 202s Building dependency tree... 202s Reading state information... 203s Calculating upgrade...Starting pkgProblemResolver with broken count: 0 203s Starting 2 pkgProblemResolver with broken count: 0 203s Done 204s Entering ResolveByKeep 204s 204s Calculating upgrade... 204s The following packages will be upgraded: 205s gir1.2-glib-2.0 libglib2.0-0t64 libglib2.0-data 205s 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 205s Need to get 1808 kB of archives. 205s After this operation, 2048 B of additional disk space will be used. 205s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 gir1.2-glib-2.0 arm64 2.83.4-1 [185 kB] 205s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 libglib2.0-0t64 arm64 2.83.4-1 [1570 kB] 205s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/main arm64 libglib2.0-data all 2.83.4-1 [52.9 kB] 206s Fetched 1808 kB in 1s (2768 kB/s) 206s (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 ... 116669 files and directories currently installed.) 208s Preparing to unpack .../gir1.2-glib-2.0_2.83.4-1_arm64.deb ... 208s Unpacking gir1.2-glib-2.0:arm64 (2.83.4-1) over (2.83.3-2) ... 208s Preparing to unpack .../libglib2.0-0t64_2.83.4-1_arm64.deb ... 208s Unpacking libglib2.0-0t64:arm64 (2.83.4-1) over (2.83.3-2) ... 208s Preparing to unpack .../libglib2.0-data_2.83.4-1_all.deb ... 208s Unpacking libglib2.0-data (2.83.4-1) over (2.83.3-2) ... 208s Setting up libglib2.0-0t64:arm64 (2.83.4-1) ... 208s No schema files found: doing nothing. 208s Setting up libglib2.0-data (2.83.4-1) ... 208s Setting up gir1.2-glib-2.0:arm64 (2.83.4-1) ... 208s Processing triggers for libc-bin (2.40-4ubuntu1) ... 208s Reading package lists... 208s Building dependency tree... 208s Reading state information... 208s Starting pkgProblemResolver with broken count: 0 208s Starting 2 pkgProblemResolver with broken count: 0 208s Done 208s Solving dependencies... 208s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 208s autopkgtest [05:00:27]: rebooting testbed after setup commands that affected boot 233s autopkgtest [05:00:52]: testbed running kernel: Linux 6.12.0-15-generic #15-Ubuntu SMP PREEMPT_DYNAMIC Tue Feb 4 15:49:33 UTC 2025 236s autopkgtest [05:00:55]: @@@@@@@@@@@@@@@@@@@@ apt-source libfprint 242s Get:1 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.9+tod1-1 (dsc) [2943 B] 242s Get:2 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.9+tod1-1 (tar) [9291 kB] 242s Get:3 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.9+tod1-1 (diff) [17.8 kB] 242s gpgv: Signature made Thu Feb 20 18:31:16 2025 UTC 242s gpgv: using RSA key D4C501DA48EB797A081750939449C2F50996635F 242s gpgv: Can't check signature: No public key 242s dpkg-source: warning: cannot verify inline signature for ./libfprint_1.94.9+tod1-1.dsc: no acceptable signature found 244s autopkgtest [05:01:03]: testing package libfprint version 1:1.94.9+tod1-1 245s autopkgtest [05:01:04]: build not needed 247s autopkgtest [05:01:06]: test installed-tests: preparing testbed 247s Reading package lists... 248s Building dependency tree... 248s Reading state information... 248s Starting pkgProblemResolver with broken count: 0 248s Starting 2 pkgProblemResolver with broken count: 0 248s Done 249s The following NEW packages will be installed: 249s fontconfig-config fonts-dejavu-core fonts-dejavu-mono gir1.2-fprint-2.0 249s gir1.2-gusb-1.0 gir1.2-json-1.0 gnome-desktop-testing libcairo2 249s libfontconfig1 libfprint-2-2 libfprint-2-tests libfprint-2-tod1 libgusb2 249s libpixman-1-0 libumockdev0 libxcb-render0 libxcb-shm0 libxrender1 249s python3-cairo umockdev 249s 0 upgraded, 20 newly installed, 0 to remove and 0 not upgraded. 249s Need to get 9583 kB of archives. 249s After this operation, 34.4 MB of additional disk space will be used. 249s Get:1 http://ftpmaster.internal/ubuntu plucky/main arm64 fonts-dejavu-mono all 2.37-8 [502 kB] 249s Get:2 http://ftpmaster.internal/ubuntu plucky/main arm64 fonts-dejavu-core all 2.37-8 [835 kB] 249s Get:3 http://ftpmaster.internal/ubuntu plucky/main arm64 fontconfig-config arm64 2.15.0-2ubuntu1 [37.5 kB] 249s Get:4 http://ftpmaster.internal/ubuntu plucky/main arm64 gir1.2-json-1.0 arm64 1.10.6+ds-1 [9992 B] 249s Get:5 http://ftpmaster.internal/ubuntu plucky/main arm64 libgusb2 arm64 0.4.9-1 [37.8 kB] 249s Get:6 http://ftpmaster.internal/ubuntu plucky/main arm64 gir1.2-gusb-1.0 arm64 0.4.9-1 [7450 B] 249s Get:7 http://ftpmaster.internal/ubuntu plucky/main arm64 libpixman-1-0 arm64 0.44.0-3 [197 kB] 249s Get:8 http://ftpmaster.internal/ubuntu plucky/main arm64 libfprint-2-tod1 arm64 1:1.94.9+tod1-1 [63.2 kB] 249s Get:9 http://ftpmaster.internal/ubuntu plucky/main arm64 libfprint-2-2 arm64 1:1.94.9+tod1-1 [268 kB] 249s Get:10 http://ftpmaster.internal/ubuntu plucky/main arm64 gir1.2-fprint-2.0 arm64 1:1.94.9+tod1-1 [7234 B] 249s Get:11 http://ftpmaster.internal/ubuntu plucky/universe arm64 gnome-desktop-testing arm64 2021.1-4 [16.2 kB] 250s Get:12 http://ftpmaster.internal/ubuntu plucky/main arm64 libfontconfig1 arm64 2.15.0-2ubuntu1 [144 kB] 250s Get:13 http://ftpmaster.internal/ubuntu plucky/main arm64 libxcb-render0 arm64 1.17.0-2 [16.6 kB] 250s Get:14 http://ftpmaster.internal/ubuntu plucky/main arm64 libxcb-shm0 arm64 1.17.0-2 [5884 B] 250s Get:15 http://ftpmaster.internal/ubuntu plucky/main arm64 libxrender1 arm64 1:0.9.10-1.1build1 [18.8 kB] 250s Get:16 http://ftpmaster.internal/ubuntu plucky/main arm64 libcairo2 arm64 1.18.2-2 [560 kB] 250s Get:17 http://ftpmaster.internal/ubuntu plucky/main arm64 python3-cairo arm64 1.26.1-2build1 [139 kB] 250s Get:18 http://ftpmaster.internal/ubuntu plucky/universe arm64 libumockdev0 arm64 0.19.1-3 [74.0 kB] 250s Get:19 http://ftpmaster.internal/ubuntu plucky/universe arm64 umockdev arm64 0.19.1-3 [73.1 kB] 250s Get:20 http://ftpmaster.internal/ubuntu plucky/universe arm64 libfprint-2-tests arm64 1:1.94.9+tod1-1 [6570 kB] 250s Fetched 9583 kB in 1s (9275 kB/s) 250s Selecting previously unselected package fonts-dejavu-mono. 251s (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 ... 116669 files and directories currently installed.) 251s Preparing to unpack .../00-fonts-dejavu-mono_2.37-8_all.deb ... 251s Unpacking fonts-dejavu-mono (2.37-8) ... 251s Selecting previously unselected package fonts-dejavu-core. 251s Preparing to unpack .../01-fonts-dejavu-core_2.37-8_all.deb ... 251s Unpacking fonts-dejavu-core (2.37-8) ... 251s Selecting previously unselected package fontconfig-config. 251s Preparing to unpack .../02-fontconfig-config_2.15.0-2ubuntu1_arm64.deb ... 251s Unpacking fontconfig-config (2.15.0-2ubuntu1) ... 251s Selecting previously unselected package gir1.2-json-1.0:arm64. 251s Preparing to unpack .../03-gir1.2-json-1.0_1.10.6+ds-1_arm64.deb ... 251s Unpacking gir1.2-json-1.0:arm64 (1.10.6+ds-1) ... 251s Selecting previously unselected package libgusb2:arm64. 251s Preparing to unpack .../04-libgusb2_0.4.9-1_arm64.deb ... 251s Unpacking libgusb2:arm64 (0.4.9-1) ... 251s Selecting previously unselected package gir1.2-gusb-1.0:arm64. 251s Preparing to unpack .../05-gir1.2-gusb-1.0_0.4.9-1_arm64.deb ... 251s Unpacking gir1.2-gusb-1.0:arm64 (0.4.9-1) ... 251s Selecting previously unselected package libpixman-1-0:arm64. 251s Preparing to unpack .../06-libpixman-1-0_0.44.0-3_arm64.deb ... 251s Unpacking libpixman-1-0:arm64 (0.44.0-3) ... 251s Selecting previously unselected package libfprint-2-tod1:arm64. 251s Preparing to unpack .../07-libfprint-2-tod1_1%3a1.94.9+tod1-1_arm64.deb ... 251s Unpacking libfprint-2-tod1:arm64 (1:1.94.9+tod1-1) ... 251s Selecting previously unselected package libfprint-2-2. 251s Preparing to unpack .../08-libfprint-2-2_1%3a1.94.9+tod1-1_arm64.deb ... 251s Unpacking libfprint-2-2 (1:1.94.9+tod1-1) ... 251s Selecting previously unselected package gir1.2-fprint-2.0:arm64. 251s Preparing to unpack .../09-gir1.2-fprint-2.0_1%3a1.94.9+tod1-1_arm64.deb ... 251s Unpacking gir1.2-fprint-2.0:arm64 (1:1.94.9+tod1-1) ... 251s Selecting previously unselected package gnome-desktop-testing. 251s Preparing to unpack .../10-gnome-desktop-testing_2021.1-4_arm64.deb ... 251s Unpacking gnome-desktop-testing (2021.1-4) ... 251s Selecting previously unselected package libfontconfig1:arm64. 251s Preparing to unpack .../11-libfontconfig1_2.15.0-2ubuntu1_arm64.deb ... 251s Unpacking libfontconfig1:arm64 (2.15.0-2ubuntu1) ... 251s Selecting previously unselected package libxcb-render0:arm64. 251s Preparing to unpack .../12-libxcb-render0_1.17.0-2_arm64.deb ... 251s Unpacking libxcb-render0:arm64 (1.17.0-2) ... 251s Selecting previously unselected package libxcb-shm0:arm64. 251s Preparing to unpack .../13-libxcb-shm0_1.17.0-2_arm64.deb ... 251s Unpacking libxcb-shm0:arm64 (1.17.0-2) ... 251s Selecting previously unselected package libxrender1:arm64. 251s Preparing to unpack .../14-libxrender1_1%3a0.9.10-1.1build1_arm64.deb ... 251s Unpacking libxrender1:arm64 (1:0.9.10-1.1build1) ... 252s Selecting previously unselected package libcairo2:arm64. 252s Preparing to unpack .../15-libcairo2_1.18.2-2_arm64.deb ... 252s Unpacking libcairo2:arm64 (1.18.2-2) ... 252s Selecting previously unselected package python3-cairo. 252s Preparing to unpack .../16-python3-cairo_1.26.1-2build1_arm64.deb ... 252s Unpacking python3-cairo (1.26.1-2build1) ... 252s Selecting previously unselected package libumockdev0:arm64. 252s Preparing to unpack .../17-libumockdev0_0.19.1-3_arm64.deb ... 252s Unpacking libumockdev0:arm64 (0.19.1-3) ... 252s Selecting previously unselected package umockdev. 252s Preparing to unpack .../18-umockdev_0.19.1-3_arm64.deb ... 252s Unpacking umockdev (0.19.1-3) ... 252s Selecting previously unselected package libfprint-2-tests. 252s Preparing to unpack .../19-libfprint-2-tests_1%3a1.94.9+tod1-1_arm64.deb ... 252s Unpacking libfprint-2-tests (1:1.94.9+tod1-1) ... 252s Setting up gnome-desktop-testing (2021.1-4) ... 252s Setting up libpixman-1-0:arm64 (0.44.0-3) ... 252s Setting up libxrender1:arm64 (1:0.9.10-1.1build1) ... 252s Setting up libxcb-render0:arm64 (1.17.0-2) ... 252s Setting up libgusb2:arm64 (0.4.9-1) ... 252s Setting up libfprint-2-tod1:arm64 (1:1.94.9+tod1-1) ... 252s Setting up libxcb-shm0:arm64 (1.17.0-2) ... 252s Setting up fonts-dejavu-mono (2.37-8) ... 252s Setting up fonts-dejavu-core (2.37-8) ... 252s Setting up libumockdev0:arm64 (0.19.1-3) ... 252s Setting up gir1.2-json-1.0:arm64 (1.10.6+ds-1) ... 252s Setting up libfprint-2-2 (1:1.94.9+tod1-1) ... 261s Setting up umockdev (0.19.1-3) ... 261s Setting up fontconfig-config (2.15.0-2ubuntu1) ... 262s Setting up gir1.2-gusb-1.0:arm64 (0.4.9-1) ... 262s Setting up libfontconfig1:arm64 (2.15.0-2ubuntu1) ... 262s Setting up gir1.2-fprint-2.0:arm64 (1:1.94.9+tod1-1) ... 262s Setting up libcairo2:arm64 (1.18.2-2) ... 262s Setting up python3-cairo (1.26.1-2build1) ... 262s Setting up libfprint-2-tests (1:1.94.9+tod1-1) ... 262s Processing triggers for man-db (2.13.0-1) ... 262s Processing triggers for udev (257.2-3ubuntu1) ... 263s Processing triggers for libc-bin (2.40-4ubuntu1) ... 264s autopkgtest [05:01:23]: test installed-tests: gnome-desktop-testing-runner libfprint-2 264s autopkgtest [05:01:23]: test installed-tests: [----------------------- 264s Running test: libfprint-2/driver-elanspi.test 264s ** (umockdev-run:2277): DEBUG: 05:01:23.786: umockdev.vala:127: Created udev test bed /tmp/umockdev.WQE312 264s ** (umockdev-run:2277): DEBUG: 05:01:23.786: 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 264s ** (umockdev-run:2277): DEBUG: 05:01:23.786: 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) 264s ** (umockdev-run:2277): DEBUG: 05:01:23.787: umockdev.vala:1558: create_node_for_device: creating pty device /tmp/umockdev.WQE312/dev/spidev0.0: got pty /dev/pts/0 264s ** (umockdev-run:2277): DEBUG: 05:01:23.788: umockdev.vala:1579: create_node_for_device: creating ptymap symlink /tmp/umockdev.WQE312/dev/.ptymap/_dev_pts_0 264s ** (umockdev-run:2277): DEBUG: 05:01:23.788: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 264s ** (umockdev-run:2277): DEBUG: 05:01:23.788: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0/spi-ELAN7001:00 (subsystem spi) 264s ** (umockdev-run:2277): DEBUG: 05:01:23.790: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 264s ** (umockdev-run:2277): DEBUG: 05:01:23.790: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3/spi_master/spi0 (subsystem spi_master) 264s ** (umockdev-run:2277): DEBUG: 05:01:23.792: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 264s ** (umockdev-run:2277): DEBUG: 05:01:23.792: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2/pxa2xx-spi.3 (subsystem platform) 264s ** (umockdev-run:2277): DEBUG: 05:01:23.792: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1e.2 264s ** (umockdev-run:2277): DEBUG: 05:01:23.792: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1e.2 (subsystem pci) 264s ** (umockdev-run:2277): DEBUG: 05:01:23.794: 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 264s ** (umockdev-run:2277): DEBUG: 05:01:23.794: 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) 264s ** (umockdev-run:2277): DEBUG: 05:01:23.795: umockdev.vala:1558: create_node_for_device: creating pty device /tmp/umockdev.WQE312/dev/hidraw0: got pty /dev/pts/1 264s ** (umockdev-run:2277): DEBUG: 05:01:23.795: umockdev.vala:1579: create_node_for_device: creating ptymap symlink /tmp/umockdev.WQE312/dev/.ptymap/_dev_pts_1 264s ** (umockdev-run:2277): DEBUG: 05:01:23.795: 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 264s ** (umockdev-run:2277): DEBUG: 05:01:23.795: 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) 264s ** (umockdev-run:2277): DEBUG: 05:01:23.796: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 264s ** (umockdev-run:2277): DEBUG: 05:01:23.796: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1/i2c-ELAN1300:00 (subsystem i2c) 264s ** (umockdev-run:2277): DEBUG: 05:01:23.796: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 264s ** (umockdev-run:2277): DEBUG: 05:01:23.797: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-1 (subsystem i2c) 264s ** (umockdev-run:2277): DEBUG: 05:01:23.797: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1/i2c_designware.1 264s ** (umockdev-run:2277): DEBUG: 05:01:23.797: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1/i2c_designware.1 (subsystem platform) 264s ** (umockdev-run:2277): DEBUG: 05:01:23.798: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:15.1 264s ** (umockdev-run:2277): DEBUG: 05:01:23.798: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:15.1 (subsystem pci) 264s (umockdev-run:2277): GLib-GIO-DEBUG: 05:01:23.799: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 265s (process:2281): libfprint-context-DEBUG: 05:01:24.011: Initializing FpContext (libfprint version 1.94.9+tod1) 265s (process:2281): libfprint-tod-DEBUG: 05:01:24.013: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 265s (process:2281): libfprint-device-DEBUG: 05:01:24.016: Device reported probe completion 265s (process:2281): libfprint-device-DEBUG: 05:01:24.016: Completing action FPI_DEVICE_ACTION_PROBE in idle! 265s (process:2281): libfprint-device-DEBUG: 05:01:24.016: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.017: 41935779: ../libfprint/drivers/elanspi.c:1562 265s (process:2281): libfprint-image_device-DEBUG: 05:01:24.018: Image device open completed 265s (process:2281): libfprint-device-DEBUG: 05:01:24.018: Device reported open completion 265s (process:2281): libfprint-device-DEBUG: 05:01:24.018: Completing action FPI_DEVICE_ACTION_OPEN in idle! 265s (process:2281): libfprint-device-DEBUG: 05:01:24.018: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:2281): libfprint-device-DEBUG: 05:01:24.018: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 265s (process:2281): libfprint-image_device-DEBUG: 05:01:24.018: Activating image device 265s (process:2281): libfprint-image_device-DEBUG: 05:01:24.018: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.018: [elanspi] ELANSPI_INIT_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.019: [elanspi] ELANSPI_INIT_NSTATES entering state 1 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.019: got status 81 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.019: sync hw reset 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.020: [elanspi] ELANSPI_INIT_NSTATES entering state 2 265s libfprint-Message: 05:01:24.019: Failed to read spidev block size, using 4096 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.024: [elanspi] ELANSPI_INIT_NSTATES entering state 3 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.024: sw reset ok 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.025: [elanspi] ELANSPI_INIT_NSTATES entering state 4 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.025: raw height = 96 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.025: [elanspi] ELANSPI_INIT_NSTATES entering state 5 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.025: raw width = 96 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.026: [elanspi] ELANSPI_INIT_NSTATES entering state 6 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.026: raw reg17 = 175 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.026: [elanspi] ELANSPI_INIT_NSTATES entering state 7 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.026: raw version = 09 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.026: after hardcoded lookup; 96x96, version 1 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.026: found sensor ID 6 => [eFSA96SA] (96 x 96) 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.026: [elanspi] ELANSPI_INIT_NSTATES entering state 8 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.030: [elanspi] ELANSPI_INIT_NSTATES entering state 9 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.031: [elanspi] ELANSPI_INIT_NSTATES entering state 10 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.031: [elanspi] ELANSPI_INIT_NSTATES entering state 11 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.031: [elanspi] ELANSPI_INIT_NSTATES entering state 12 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.032: [elanspi] ELANSPI_INIT_NSTATES entering state 13 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.032: [elanspi] ELANSPI_INIT_NSTATES entering state 14 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.032: [elanspi] ELANSPI_INIT_NSTATES entering state 17 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.032: got vcm mode = 2 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.032: [elanspi] ELANSPI_INIT_NSTATES entering state 18 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.033: [elanspi] ELANSPI_INIT_NSTATES entering state 19 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.033: starting calibrate 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.033: [elanspi] old calibrate entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.034: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.035: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.035: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.035: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.035: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.035: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.035: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.035: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.035: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.036: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.036: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.036: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.036: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.036: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.036: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.036: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.036: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.036: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.036: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.037: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.037: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.037: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.037: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.037: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.037: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.037: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.037: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.038: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.038: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.038: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.038: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.038: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.038: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.038: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.038: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.039: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.039: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.039: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.039: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.039: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.039: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.039: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.039: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.039: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.039: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.040: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.040: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.040: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.040: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.040: [elanspi] ELANSPI_WRTABLE_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.040: [elanspi] ELANSPI_WRTABLE_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.040: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.093: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.093: dac init is 0x29 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.093: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-device-DEBUG: 05:01:24.118: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.145: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.145: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.202: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.203: calibration ok, saving bg image 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.203: [elanspi] old calibrate completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.203: [elanspi] ELANSPI_INIT_NSTATES entering state 20 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.203: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.260: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.260: [elanspi] ELANSPI_INIT_NSTATES entering state 21 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.260: [elanspi] ELANSPI_INIT_NSTATES completed successfully 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.260: 42179085: ../libfprint/drivers/elanspi.c:1596 265s (process:2281): libfprint-image_device-DEBUG: 05:01:24.260: Image device activation completed 265s (process:2281): libfprint-image_device-DEBUG: 05:01:24.260: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 265s (process:2281): libfprint-image_device-DEBUG: 05:01:24.260: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.260: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.260: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.260: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.260: started capturer 265s (process:2281): libfprint-device-DEBUG: 05:01:24.260: Device reported finger status change: FP_FINGER_STATUS_NEEDED 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.317: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.317: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.317: stddev=933d, ip=40, is_fp=0, is_empty=2 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.317: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.317: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.373: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.373: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.373: stddev=829d, ip=48, is_fp=0, is_empty=2 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.373: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.373: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.429: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.429: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.430: stddev=1307d, ip=37, is_fp=0, is_empty=2 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.430: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.430: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.482: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.482: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.483: stddev=1163d, ip=38, is_fp=0, is_empty=2 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.483: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.483: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.537: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.537: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.537: stddev=960d, ip=43, is_fp=0, is_empty=2 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.537: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.537: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.593: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.593: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.593: stddev=879d, ip=41, is_fp=0, is_empty=2 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.593: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.593: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.643: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.643: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.644: stddev=925d, ip=44, is_fp=0, is_empty=2 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.644: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.644: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.696: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.696: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.696: stddev=1244d, ip=37, is_fp=0, is_empty=2 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.696: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.696: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.751: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.751: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.751: stddev=709d, ip=48, is_fp=0, is_empty=2 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.751: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.751: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.801: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.801: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.801: stddev=553d, ip=54, is_fp=0, is_empty=2 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.801: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.801: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.859: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.859: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.859: stddev=904d, ip=44, is_fp=0, is_empty=2 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.859: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.859: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.915: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.915: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 265s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.916: stddev=951d, ip=46, is_fp=0, is_empty=2 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.916: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 265s (process:2281): libfprint-SSM-DEBUG: 05:01:24.916: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:24.969: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:24.969: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:24.970: stddev=795d, ip=44, is_fp=0, is_empty=2 266s (process:2281): libfprint-SSM-DEBUG: 05:01:24.970: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 266s (process:2281): libfprint-SSM-DEBUG: 05:01:24.970: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.025: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.025: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.026: stddev=985d, ip=41, is_fp=0, is_empty=2 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.026: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.026: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.083: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.083: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.083: stddev=938d, ip=40, is_fp=0, is_empty=2 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.083: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.083: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.141: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.141: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.142: stddev=846d, ip=40, is_fp=0, is_empty=2 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.142: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.142: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.199: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.199: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.199: stddev=693d, ip=56, is_fp=0, is_empty=2 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.199: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.199: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.256: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.256: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.256: stddev=777d, ip=50, is_fp=0, is_empty=2 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.256: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.256: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.312: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.312: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.312: stddev=824d, ip=45, is_fp=0, is_empty=2 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.312: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.312: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.367: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.367: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.367: stddev=521d, ip=50, is_fp=0, is_empty=2 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.367: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.367: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.422: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.422: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.422: stddev=670d, ip=47, is_fp=0, is_empty=2 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.422: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.422: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.480: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.480: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.480: stddev=1262d, ip=39, is_fp=0, is_empty=2 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.480: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.480: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.539: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.539: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.539: stddev=912d, ip=42, is_fp=0, is_empty=2 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.539: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.539: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.588: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.588: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.588: stddev=1402d, ip=37, is_fp=0, is_empty=2 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.588: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.588: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.639: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.639: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.639: stddev=1530d, ip=32, is_fp=0, is_empty=2 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.639: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.639: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.688: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.688: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.688: stddev=718159d, ip=6, is_fp=1, is_empty=0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.688: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 1 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.688: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.736: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.736: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 2 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.736: stddev=400929d, ip=0, is_fp=2, is_empty=0 266s (process:2281): libfprint-device-DEBUG: 05:01:25.736: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 266s (process:2281): libfprint-image_device-DEBUG: 05:01:25.736: Image device reported finger status: on 266s (process:2281): libfprint-image_device-DEBUG: 05:01:25.736: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.736: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.736: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.783: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.783: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.784: stddev=346514d, ip=0, is_fp=1, is_empty=0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.784: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.784: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.830: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.830: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.830: stddev=324160d, ip=0, is_fp=1, is_empty=0 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.831: diff = 107344 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.831: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.831: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.876: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.876: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.876: stddev=339430d, ip=0, is_fp=1, is_empty=0 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.877: diff = 246471 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.877: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.877: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.923: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.923: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.923: stddev=334711d, ip=0, is_fp=1, is_empty=0 266s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.924: diff = 73010 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.924: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 266s (process:2281): libfprint-SSM-DEBUG: 05:01:25.924: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:25.969: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:25.969: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.969: stddev=317574d, ip=0, is_fp=1, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.969: diff = 58831 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:25.969: ignoring b.c. difference is too small 267s (process:2281): libfprint-SSM-DEBUG: 05:01:25.969: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:25.970: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.020: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.020: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.020: stddev=285577d, ip=0, is_fp=1, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.020: diff = 241923 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.020: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.020: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.070: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.070: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.070: stddev=417772d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.071: diff = 254823 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.071: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.071: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.122: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.122: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.122: stddev=541148d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.123: diff = 290922 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.123: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.123: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.174: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.174: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.174: stddev=580192d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.175: diff = 332283 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.175: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.175: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.225: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.225: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.225: stddev=484527d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.226: diff = 325141 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.226: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.226: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.280: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.280: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.281: stddev=482100d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.281: diff = 337412 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.281: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.281: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.328: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.328: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.328: stddev=558238d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.329: diff = 342841 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.329: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.329: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.381: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.381: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.381: stddev=572990d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.382: diff = 352690 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.382: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.382: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.428: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.428: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.428: stddev=575411d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.429: diff = 365537 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.429: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.429: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.474: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.474: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.475: stddev=578482d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.475: diff = 342041 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.475: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.475: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.521: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.521: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.521: stddev=572686d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.522: diff = 421037 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.522: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.522: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.567: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.567: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.568: stddev=465498d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.568: diff = 404640 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.568: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.568: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.625: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.625: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.625: stddev=410135d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.626: diff = 347658 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.626: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.626: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.684: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.684: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.684: stddev=493239d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.685: diff = 344237 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.685: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.685: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.742: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.742: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.742: stddev=553028d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.743: diff = 419597 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.743: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.743: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.799: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.799: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.800: stddev=574502d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.800: diff = 408934 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.800: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.800: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.855: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.855: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.856: stddev=645815d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.856: diff = 409198 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.856: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.856: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.911: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.911: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.912: stddev=677451d, ip=0, is_fp=2, is_empty=0 267s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.912: diff = 429666 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.912: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 3 267s (process:2281): libfprint-SSM-DEBUG: 05:01:26.912: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:26.968: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 268s (process:2281): libfprint-SSM-DEBUG: 05:01:26.968: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 4 268s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.968: stddev=634407d, ip=0, is_fp=2, is_empty=0 268s (process:2281): libfprint-elanspi-DEBUG: 05:01:26.968: have enough frames, exiting now 268s (process:2281): libfprint-assembling-DEBUG: 05:01:27.135: calc delta completed in 0.166911 secs 268s (process:2281): libfprint-assembling-DEBUG: 05:01:27.302: calc delta completed in 0.166519 secs 268s (process:2281): libfprint-assembling-DEBUG: 05:01:27.302: errors: 86516 rev: 170625 268s (process:2281): libfprint-assembling-DEBUG: 05:01:27.468: calc delta completed in 0.166218 secs 268s (process:2281): libfprint-assembling-DEBUG: 05:01:27.468: height is 246 268s (process:2281): libfprint-image_device-DEBUG: 05:01:27.471: Image device captured an image 268s (process:2281): libfprint-image_device-DEBUG: 05:01:27.471: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 268s (process:2281): libfprint-device-DEBUG: 05:01:27.471: Device reported finger status change: FP_FINGER_STATUS_PRESENT 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.471: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.471: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.518: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.518: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 268s (process:2281): libfprint-elanspi-DEBUG: 05:01:27.518: stddev=593525d, ip=0, is_fp=2, is_empty=0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.518: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.518: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 268s (process:2281): libfprint-image-DEBUG: 05:01:27.520: Minutiae scan completed in 0.048938 secs 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.571: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.571: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 268s (process:2281): libfprint-elanspi-DEBUG: 05:01:27.571: stddev=610651d, ip=0, is_fp=2, is_empty=0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.571: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.571: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.624: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.624: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 268s (process:2281): libfprint-elanspi-DEBUG: 05:01:27.625: stddev=505673d, ip=0, is_fp=2, is_empty=0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.625: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.625: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.679: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.679: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 268s (process:2281): libfprint-elanspi-DEBUG: 05:01:27.680: stddev=537580d, ip=0, is_fp=2, is_empty=0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.680: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.680: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.738: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.738: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 268s (process:2281): libfprint-elanspi-DEBUG: 05:01:27.738: stddev=520750d, ip=0, is_fp=2, is_empty=0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.738: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.738: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.793: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.794: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 268s (process:2281): libfprint-elanspi-DEBUG: 05:01:27.794: stddev=468008d, ip=0, is_fp=2, is_empty=0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.794: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.794: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.848: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.848: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 268s (process:2281): libfprint-elanspi-DEBUG: 05:01:27.848: stddev=477058d, ip=0, is_fp=2, is_empty=0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.848: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.848: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.903: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.903: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 268s (process:2281): libfprint-elanspi-DEBUG: 05:01:27.903: stddev=460178d, ip=0, is_fp=2, is_empty=0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.903: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.903: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.958: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.958: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 268s (process:2281): libfprint-elanspi-DEBUG: 05:01:27.958: stddev=538508d, ip=0, is_fp=2, is_empty=0 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.958: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 268s (process:2281): libfprint-SSM-DEBUG: 05:01:27.958: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.014: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.014: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 269s (process:2281): libfprint-elanspi-DEBUG: 05:01:28.015: stddev=661673d, ip=0, is_fp=2, is_empty=0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.015: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.015: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.069: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.069: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 269s (process:2281): libfprint-elanspi-DEBUG: 05:01:28.070: stddev=764706d, ip=0, is_fp=2, is_empty=0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.070: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.070: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.128: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.128: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 269s (process:2281): libfprint-elanspi-DEBUG: 05:01:28.128: stddev=806415d, ip=0, is_fp=2, is_empty=0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.128: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.128: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.184: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.184: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 269s (process:2281): libfprint-elanspi-DEBUG: 05:01:28.184: stddev=806649d, ip=0, is_fp=2, is_empty=0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.184: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.184: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.240: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.240: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 269s (process:2281): libfprint-elanspi-DEBUG: 05:01:28.240: stddev=822567d, ip=0, is_fp=2, is_empty=0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.240: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.240: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.294: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.294: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 269s (process:2281): libfprint-elanspi-DEBUG: 05:01:28.295: stddev=1017068d, ip=0, is_fp=2, is_empty=0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.295: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.295: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.349: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.349: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 269s (process:2281): libfprint-elanspi-DEBUG: 05:01:28.350: stddev=1004196d, ip=0, is_fp=2, is_empty=0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.350: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.350: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.404: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.404: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 269s (process:2281): libfprint-elanspi-DEBUG: 05:01:28.404: stddev=963655d, ip=0, is_fp=2, is_empty=0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.404: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.404: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.458: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.458: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 269s (process:2281): libfprint-elanspi-DEBUG: 05:01:28.458: stddev=880521d, ip=0, is_fp=2, is_empty=0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.458: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.458: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.515: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.515: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 269s (process:2281): libfprint-elanspi-DEBUG: 05:01:28.515: stddev=1135372d, ip=0, is_fp=2, is_empty=0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.515: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.515: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.572: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.572: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 269s (process:2281): libfprint-elanspi-DEBUG: 05:01:28.573: stddev=1093450d, ip=3, is_fp=1, is_empty=0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.573: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.573: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.627: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.627: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 269s (process:2281): libfprint-elanspi-DEBUG: 05:01:28.627: stddev=41090d, ip=8, is_fp=0, is_empty=2 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.627: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 5 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.627: [elanspi] ELANSPI_CAPTOLD_NSTATES entering state 0 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.683: [elanspi] ELANSPI_CAPTOLD_NSTATES completed successfully 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.683: [elanspi] ELANSPI_FPCAPT_NSTATES entering state 6 269s (process:2281): libfprint-elanspi-DEBUG: 05:01:28.683: stddev=6836d, ip=13, is_fp=0, is_empty=2 269s (process:2281): libfprint-device-DEBUG: 05:01:28.683: Device reported finger status change: FP_FINGER_STATUS_NONE 269s (process:2281): libfprint-image_device-DEBUG: 05:01:28.683: Image device reported finger status: off 269s (process:2281): libfprint-image_device-DEBUG: 05:01:28.683: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 269s (process:2281): libfprint-image_device-DEBUG: 05:01:28.683: Deactivating image device 269s (process:2281): libfprint-image_device-DEBUG: 05:01:28.683: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 269s (process:2281): libfprint-image_device-DEBUG: 05:01:28.683: Image device deactivation completed 269s (process:2281): libfprint-image_device-DEBUG: 05:01:28.683: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 269s (process:2281): libfprint-device-DEBUG: 05:01:28.683: Device reported capture completion 269s (process:2281): libfprint-SSM-DEBUG: 05:01:28.683: [elanspi] ELANSPI_FPCAPT_NSTATES completed successfully 269s (process:2281): libfprint-device-DEBUG: 05:01:28.683: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 269s (process:2281): libfprint-device-DEBUG: 05:01:28.683: Updated temperature model after 4.57 seconds, ratio 0.27 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 269s (process:2281): libfprint-image_device-DEBUG: 05:01:28.683: Image device close completed 269s (process:2281): libfprint-device-DEBUG: 05:01:28.683: Device reported close completion 269s (process:2281): libfprint-device-DEBUG: 05:01:28.683: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 269s (process:2281): libfprint-device-DEBUG: 05:01:28.683: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 269s ** (umockdev-run:2277): DEBUG: 05:01:28.931: umockdev.vala:154: Removing test bed /tmp/umockdev.WQE312 269s (umockdev-run:2277): GLib-DEBUG: 05:01:28.938: unsetenv() is not thread-safe and should not be used after threads are created 270s Comparing PNGs /tmp/libfprint-umockdev-test-a51dsp4r/capture.png and /usr/share/installed-tests/libfprint-2/elanspi/capture.png 270s PASS: libfprint-2/driver-elanspi.test 270s Running test: libfprint-2/driver-egismoc.test 270s ** (umockdev-run:2292): DEBUG: 05:01:29.051: umockdev.vala:127: Created udev test bed /tmp/umockdev.QO4C22 270s ** (umockdev-run:2292): DEBUG: 05:01:29.052: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 270s ** (umockdev-run:2292): DEBUG: 05:01:29.053: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 270s ** (umockdev-run:2292): DEBUG: 05:01:29.056: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.QO4C22/dev/bus/usb/003/012 270s ** (umockdev-run:2292): DEBUG: 05:01:29.056: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 270s ** (umockdev-run:2292): DEBUG: 05:01:29.057: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 270s ** (umockdev-run:2292): DEBUG: 05:01:29.059: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.QO4C22/dev/bus/usb/003/001 270s ** (umockdev-run:2292): DEBUG: 05:01:29.059: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 270s ** (umockdev-run:2292): DEBUG: 05:01:29.060: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 270s Executing: libfprint-2/driver-egismoc.test 270s (process:2296): libfprint-context-DEBUG: 05:01:29.166: Initializing FpContext (libfprint version 1.94.9+tod1) 270s (process:2296): libfprint-tod-DEBUG: 05:01:29.166: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.168: 47086832: ../libfprint/drivers/egismoc/egismoc.c:1597 270s (process:2296): libfprint-context-DEBUG: 05:01:29.168: No driver found for USB device 1D6B:0002 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.169: egismoc_probe enter --> 270s (process:2296): libfprint-device-DEBUG: 05:01:29.170: Device reported probe completion 270s (process:2296): libfprint-device-DEBUG: 05:01:29.170: Completing action FPI_DEVICE_ACTION_PROBE in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.170: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.171: Opening device 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.172: [egismoc] DEV_INIT_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.173: [egismoc] DEV_INIT_STATES entering state 1 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.173: [egismoc] DEV_INIT_STATES entering state 2 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.174: [egismoc] DEV_INIT_STATES entering state 3 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.174: [egismoc] DEV_INIT_STATES entering state 4 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.175: [egismoc] DEV_INIT_STATES entering state 5 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.175: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.175: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.175: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.176: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.176: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.176: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.176: Firmware version callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.176: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.176: Device firmware version is 9050.1.1.81 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.176: [egismoc] DEV_INIT_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.176: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.176: Device reported open completion 270s (process:2296): libfprint-device-DEBUG: 05:01:29.176: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.176: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.177: List 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.177: [egismoc] LIST_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.177: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.177: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.177: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.178: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.178: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.178: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.178: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.178: Device fingerprint 1: FP1-20231016-1-AAA9163E-root 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.178: Device fingerprint 2: FP1-20231016-2-5102A0A3-root 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.178: Device fingerprint 3: FP1-20231016-3-5159A026-root 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.178: Device fingerprint 4: FP1-20231016-4-A25C1212-root 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.178: Device fingerprint 5: FP1-20231016-5-EC893AA9-root 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.178: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.178: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.178: Number of currently enrolled fingerprints on the device is 7 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.178: [egismoc] LIST_STATES entering state 1 270s (process:2296): libfprint-device-DEBUG: 05:01:29.178: Device reported listing completion 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.178: [egismoc] LIST_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.178: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.178: Completing action FPI_DEVICE_ACTION_LIST in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.178: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.179: Clear storage 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.179: [egismoc] DELETE_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.179: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.179: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.179: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.179: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.180: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.180: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.180: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.180: Device fingerprint 1: FP1-20231016-1-AAA9163E-root 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.180: Device fingerprint 2: FP1-20231016-2-5102A0A3-root 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.180: Device fingerprint 3: FP1-20231016-3-5159A026-root 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.180: Device fingerprint 4: FP1-20231016-4-A25C1212-root 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.180: Device fingerprint 5: FP1-20231016-5-EC893AA9-root 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.180: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN( 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.180: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.180: Number of currently enrolled fingerprints on the device is 7 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.180: [egismoc] DELETE_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.180: Get delete command 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.180: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.180: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.180: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.181: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.181: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.181: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.181: Delete callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.181: Response prefix valid: yes 270s (process:2296): libfprint-device-DEBUG: 05:01:29.181: Device reported deletion completion 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.181: [egismoc] DELETE_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.181: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.181: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.181: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.181: List 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.181: [egismoc] LIST_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.181: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.181: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.181: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.182: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.183: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.183: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.183: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.183: Number of currently enrolled fingerprints on the device is 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.183: [egismoc] LIST_STATES entering state 1 270s (process:2296): libfprint-device-DEBUG: 05:01:29.183: Device reported listing completion 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.183: [egismoc] LIST_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.183: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.183: Completing action FPI_DEVICE_ACTION_LIST in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.183: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:2296): libfprint-device-DEBUG: 05:01:29.184: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.184: Enroll 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.184: [egismoc] ENROLL_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.184: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.184: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.184: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.184: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.185: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.185: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.185: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.185: Number of currently enrolled fingerprints on the device is 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.185: [egismoc] ENROLL_STATES entering state 1 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.185: [egismoc] ENROLL_STATES entering state 2 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.185: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.185: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.185: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.186: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.186: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.186: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.186: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.186: [egismoc] ENROLL_STATES entering state 3 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.186: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.186: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.186: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.187: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.187: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.187: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.187: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.187: [egismoc] ENROLL_STATES entering state 4 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.187: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.187: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.188: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.188: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.188: [egismoc] ENROLL_STATES entering state 5 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.188: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.188: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.188: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.189: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.189: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.189: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.189: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.189: [egismoc] ENROLL_STATES entering state 6 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.189: Get check command 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.189: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.189: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.189: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.190: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.191: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.191: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.191: Enroll check callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.191: Response suffix valid: yes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.191: [egismoc] ENROLL_STATES entering state 7 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.191: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.191: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.191: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.191: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.192: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.192: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.192: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.192: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.192: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.192: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.192: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.192: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.193: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.193: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.193: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.193: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.193: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.193: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.193: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.194: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.194: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.194: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.194: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.194: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.194: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.195: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.195: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.195: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.195: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.195: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.195: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.195: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.196: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.196: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.196: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.196: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.196: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.196: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.196: Partial capture successful. Please touch the sensor again (1/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.196: Device reported enroll progress, reported 1 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.196: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.196: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.197: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.197: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.197: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.198: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.198: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.198: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.198: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.198: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.198: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.198: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.198: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.199: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.199: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.199: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.199: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.199: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.199: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.199: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.199: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.199: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.199: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.199: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.199: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.200: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.201: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.201: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.201: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.201: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.201: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.201: Partial capture successful. Please touch the sensor again (2/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.201: Device reported enroll progress, reported 2 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.201: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.201: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.201: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.201: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.201: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.202: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.202: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.202: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.202: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.202: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.202: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.202: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.202: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.203: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.203: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.203: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.203: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.203: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.203: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.204: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.204: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.204: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.204: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.204: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.204: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.204: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.205: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.205: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.205: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.205: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.205: Response suffix valid: NO 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.205: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.205: Response suffix valid: yes 270s (process:2296): libfprint-device-DEBUG: 05:01:29.205: Device reported enroll progress, reported 2 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.205: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.205: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.205: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.205: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.206: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.206: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.206: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.206: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.206: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.206: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.206: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.206: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.207: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.208: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.208: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.208: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.208: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.208: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.208: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.208: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.208: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.208: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.208: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.208: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.208: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.209: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.210: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.210: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.210: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.210: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.210: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.210: Partial capture successful. Please touch the sensor again (3/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.210: Device reported enroll progress, reported 3 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.210: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.210: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.210: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.210: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.210: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.211: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.211: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.211: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.211: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.211: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.211: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.211: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.211: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.212: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.212: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.212: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.212: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.212: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.213: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.213: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.213: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.213: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.213: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.213: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.213: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.214: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.214: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.214: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.214: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.214: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.214: Partial capture successful. Please touch the sensor again (4/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.214: Device reported enroll progress, reported 4 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.214: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.214: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.214: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.214: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.215: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.215: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.215: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.215: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.216: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.216: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.216: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.216: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.216: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.217: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.217: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.217: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.217: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.217: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.217: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.217: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.217: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.217: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.217: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.217: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.217: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.218: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.218: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.219: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.219: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.219: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.219: Response suffix valid: NO 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.219: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.219: Response suffix valid: yes 270s (process:2296): libfprint-device-DEBUG: 05:01:29.219: Device reported enroll progress, reported 4 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.219: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.219: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.219: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.219: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.219: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.220: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.220: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.220: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.220: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.220: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.220: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.220: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.220: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.221: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.221: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.221: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.221: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.221: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.221: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.221: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.221: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.221: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.221: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.221: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.221: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.222: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.223: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.223: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.223: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.223: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.223: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.223: Partial capture successful. Please touch the sensor again (5/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.223: Device reported enroll progress, reported 5 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.223: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.223: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.223: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.223: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.223: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.224: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.224: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.224: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.224: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.224: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.224: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.224: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.224: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.225: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.225: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.225: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.225: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.225: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.225: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.225: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.226: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.226: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.226: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.226: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.226: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.226: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.227: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.227: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.227: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.227: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.227: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.227: Partial capture successful. Please touch the sensor again (6/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.227: Device reported enroll progress, reported 6 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.227: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.227: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.227: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.227: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.227: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.228: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.228: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.228: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.228: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.228: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.228: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.228: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.228: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.229: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.229: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.229: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.229: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.229: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.229: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.229: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.230: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.230: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.230: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.230: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.230: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.230: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.231: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.231: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.231: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.231: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.231: Response suffix valid: NO 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.231: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.231: Response suffix valid: yes 270s (process:2296): libfprint-device-DEBUG: 05:01:29.231: Device reported enroll progress, reported 6 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.231: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.231: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.231: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.231: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.231: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.232: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.232: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.232: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.232: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.232: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.232: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.232: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.232: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.233: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.233: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.233: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.233: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.233: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.233: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.233: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.233: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.233: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.233: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.233: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.234: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.235: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.235: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.235: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.235: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.235: Response suffix valid: NO 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.235: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.235: Response suffix valid: yes 270s (process:2296): libfprint-device-DEBUG: 05:01:29.235: Device reported enroll progress, reported 6 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.235: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.235: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.235: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.235: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.235: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.236: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.236: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.236: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.236: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.236: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.236: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.236: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.236: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.237: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.237: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.237: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.237: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.237: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.237: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.238: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.238: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.238: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.238: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.238: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.238: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.238: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.239: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.239: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.239: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.239: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.239: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.239: Partial capture successful. Please touch the sensor again (7/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.239: Device reported enroll progress, reported 7 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.239: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.239: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.239: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.239: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.239: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.240: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.240: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.240: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.240: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.240: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.240: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.240: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.240: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.241: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.241: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.241: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.241: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.241: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.242: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.242: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.242: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.242: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.242: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.242: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.242: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.243: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.243: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.243: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.243: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.243: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.243: Partial capture successful. Please touch the sensor again (8/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.243: Device reported enroll progress, reported 8 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.243: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.243: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.243: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.243: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.243: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.244: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.244: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.244: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.244: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.244: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.244: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.244: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.245: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.245: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.245: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.245: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.245: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.245: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.245: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.246: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.246: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.246: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.246: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.246: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.246: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.247: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.247: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.247: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.247: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.247: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.247: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.247: Partial capture successful. Please touch the sensor again (9/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.247: Device reported enroll progress, reported 9 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.247: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.247: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.247: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.247: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.248: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.249: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.249: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.249: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.249: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.249: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.249: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.249: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.249: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.250: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.250: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.250: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.250: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.250: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.251: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.251: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.251: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.251: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.251: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.251: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.251: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.252: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.252: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.252: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.252: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.252: Response suffix valid: NO 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.252: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.252: Response suffix valid: yes 270s (process:2296): libfprint-device-DEBUG: 05:01:29.252: Device reported enroll progress, reported 9 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.252: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.252: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.252: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.252: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.253: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.253: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.253: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.253: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.253: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.253: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.253: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.253: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.254: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.255: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.255: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.255: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.255: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.255: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.255: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.255: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.255: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.255: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.255: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.255: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.255: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.256: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.257: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.257: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.257: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.257: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.257: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.257: Partial capture successful. Please touch the sensor again (10/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.257: Device reported enroll progress, reported 10 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.257: [egismoc] ENROLL_STATES entering state 12 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.257: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.257: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.257: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.257: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.258: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.258: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.258: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.258: [egismoc] ENROLL_STATES entering state 13 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.258: New fingerprint ID: FP1-00000000-2-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.258: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.258: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.258: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.259: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.259: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.259: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.260: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.260: [egismoc] ENROLL_STATES entering state 14 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.260: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.260: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.260: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.260: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.261: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.261: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.261: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.261: [egismoc] ENROLL_STATES entering state 15 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.261: Enrollment was successful! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.261: Device reported enroll completion 270s (process:2296): libfprint-device-DEBUG: 05:01:29.261: Device reported finger status change: FP_FINGER_STATUS_NONE 270s (process:2296): libfprint-device-DEBUG: 05:01:29.261: Print for finger FP_FINGER_LEFT_INDEX enrolled 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.261: [egismoc] ENROLL_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.261: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.261: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.261: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.261: List 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.261: [egismoc] LIST_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.261: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.261: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.261: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.262: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.262: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.262: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.262: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.262: Device fingerprint 1: FP1-00000000-2-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.262: Number of currently enrolled fingerprints on the device is 1 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.262: [egismoc] LIST_STATES entering state 1 270s (process:2296): libfprint-device-DEBUG: 05:01:29.262: Device reported listing completion 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.262: [egismoc] LIST_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.262: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.262: Completing action FPI_DEVICE_ACTION_LIST in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.262: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-device-DEBUG: 05:01:29.263: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.263: Identify or Verify 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.263: [egismoc] IDENTIFY_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.263: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.263: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.263: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.263: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.264: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.264: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.264: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.264: Device fingerprint 1: FP1-00000000-2-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.264: Number of currently enrolled fingerprints on the device is 1 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.264: [egismoc] IDENTIFY_STATES entering state 1 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.264: [egismoc] IDENTIFY_STATES entering state 2 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.264: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.264: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.264: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.265: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.266: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.266: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.266: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.266: [egismoc] IDENTIFY_STATES entering state 3 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.266: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.266: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.266: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.266: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.267: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.267: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.267: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.267: [egismoc] IDENTIFY_STATES entering state 4 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.267: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.267: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.268: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.268: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.268: [egismoc] IDENTIFY_STATES entering state 5 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.268: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.268: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.268: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.268: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.269: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.269: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.269: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.269: [egismoc] IDENTIFY_STATES entering state 6 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.269: Get check command 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.269: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.269: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.269: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.270: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.270: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.270: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.270: Identify check callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.270: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.270: Identify successful for: FP1-00000000-2-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.270: Verifying against: FP1-00000000-2-00000000-nobody 270s (process:2296): libfprint-device-DEBUG: 05:01:29.270: Device reported verify result 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.270: [egismoc] IDENTIFY_STATES entering state 7 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.270: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.270: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.270: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.271: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.272: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.272: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.272: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.272: [egismoc] IDENTIFY_STATES entering state 8 270s (process:2296): libfprint-device-DEBUG: 05:01:29.272: Device reported verify completion 270s (process:2296): libfprint-device-DEBUG: 05:01:29.272: Device reported finger status change: FP_FINGER_STATUS_NONE 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.272: [egismoc] IDENTIFY_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.272: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.272: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.272: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-device-DEBUG: 05:01:29.273: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.273: Identify or Verify 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.273: [egismoc] IDENTIFY_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.273: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.273: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.273: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.273: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.274: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.274: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.274: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.274: Device fingerprint 1: FP1-00000000-2-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.274: Number of currently enrolled fingerprints on the device is 1 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.274: [egismoc] IDENTIFY_STATES entering state 1 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.274: [egismoc] IDENTIFY_STATES entering state 2 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.274: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.274: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.274: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.275: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.276: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.276: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.276: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.276: [egismoc] IDENTIFY_STATES entering state 3 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.276: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.276: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.276: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.277: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.277: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.277: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.277: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.277: [egismoc] IDENTIFY_STATES entering state 4 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.277: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.277: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.278: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.278: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.278: [egismoc] IDENTIFY_STATES entering state 5 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.278: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.278: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.278: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.279: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.279: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.279: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.279: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.279: [egismoc] IDENTIFY_STATES entering state 6 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.279: Get check command 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.279: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.279: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.279: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.280: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.281: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.281: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.281: Identify check callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.281: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.281: Identify successful for: FP1-00000000-2-00000000-nobody 270s (process:2296): libfprint-device-DEBUG: 05:01:29.281: Device reported identify result 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.281: [egismoc] IDENTIFY_STATES entering state 7 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.281: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.281: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.281: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.281: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.282: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.282: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.282: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.282: [egismoc] IDENTIFY_STATES entering state 8 270s (process:2296): libfprint-device-DEBUG: 05:01:29.282: Device reported identify completion 270s (process:2296): libfprint-device-DEBUG: 05:01:29.282: Device reported finger status change: FP_FINGER_STATUS_NONE 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.282: [egismoc] IDENTIFY_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.282: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.282: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.282: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-device-DEBUG: 05:01:29.283: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.283: Enroll 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.283: [egismoc] ENROLL_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.283: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.283: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.283: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.284: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.284: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.284: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.284: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.284: Device fingerprint 1: FP1-00000000-2-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.284: Number of currently enrolled fingerprints on the device is 1 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.285: [egismoc] ENROLL_STATES entering state 1 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.285: [egismoc] ENROLL_STATES entering state 2 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.285: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.285: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.285: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.285: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.286: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.286: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.286: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.286: [egismoc] ENROLL_STATES entering state 3 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.286: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.286: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.286: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.287: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.287: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.287: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.287: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.287: [egismoc] ENROLL_STATES entering state 4 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.287: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.287: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.288: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.288: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.288: [egismoc] ENROLL_STATES entering state 5 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.288: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.288: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.288: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.288: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.289: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.289: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.289: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.289: [egismoc] ENROLL_STATES entering state 6 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.289: Get check command 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.289: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.289: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.289: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.290: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.290: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.290: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.290: Enroll check callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.290: Response suffix valid: NO 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.290: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.290: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.290: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.290: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 270s (process:2296): libfprint-device-DEBUG: 05:01:29.290: Device reported enroll completion 270s (process:2296): libfprint-device-DEBUG: 05:01:29.290: Device reported finger status change: FP_FINGER_STATUS_NONE 270s (process:2296): libfprint-device-DEBUG: 05:01:29.290: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.290: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.291: List 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.291: [egismoc] LIST_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.291: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.291: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.291: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.292: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.292: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.292: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.292: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.292: Device fingerprint 1: FP1-00000000-2-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.293: Number of currently enrolled fingerprints on the device is 1 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.293: [egismoc] LIST_STATES entering state 1 270s (process:2296): libfprint-device-DEBUG: 05:01:29.293: Device reported listing completion 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.293: [egismoc] LIST_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.293: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.293: Completing action FPI_DEVICE_ACTION_LIST in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.293: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-device-DEBUG: 05:01:29.293: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.293: Enroll 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.293: [egismoc] ENROLL_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.293: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.293: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.293: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.293: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.294: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.294: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.294: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.294: Device fingerprint 1: FP1-00000000-2-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.294: Number of currently enrolled fingerprints on the device is 1 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.294: [egismoc] ENROLL_STATES entering state 1 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.294: [egismoc] ENROLL_STATES entering state 2 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.294: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.294: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.294: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.295: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.295: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.296: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.296: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.296: [egismoc] ENROLL_STATES entering state 3 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.296: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.296: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.296: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.296: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.297: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.297: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.297: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.297: [egismoc] ENROLL_STATES entering state 4 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.297: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.297: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.297: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.297: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.297: [egismoc] ENROLL_STATES entering state 5 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.297: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.297: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.297: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.298: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.299: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.299: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.299: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.299: [egismoc] ENROLL_STATES entering state 6 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.299: Get check command 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.299: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.299: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.299: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.299: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.300: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.300: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.300: Enroll check callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.300: Response suffix valid: yes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.300: [egismoc] ENROLL_STATES entering state 7 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.300: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.300: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.300: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.300: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.301: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.301: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.301: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.301: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.301: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.301: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.301: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.302: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.302: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.302: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.302: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.302: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.302: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.302: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.302: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.303: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.304: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.304: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.304: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.304: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.304: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.304: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.304: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.304: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.304: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.304: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.304: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.304: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.305: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.306: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.306: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.306: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.306: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.306: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.306: Partial capture successful. Please touch the sensor again (1/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.306: Device reported enroll progress, reported 1 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.306: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.306: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.306: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.306: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.306: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.307: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.307: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.307: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.307: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.307: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.307: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.307: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.308: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.308: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.308: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.308: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.308: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.308: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.308: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.309: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.309: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.309: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.309: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.309: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.309: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.309: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.310: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.310: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.310: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.310: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.310: Response suffix valid: NO 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.310: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.310: Response suffix valid: yes 270s (process:2296): libfprint-device-DEBUG: 05:01:29.310: Device reported enroll progress, reported 1 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.310: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.310: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.310: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.310: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.311: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.311: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.312: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.312: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.312: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.312: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.312: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.312: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.312: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.313: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.313: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.313: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.313: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.313: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.313: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.314: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.314: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.314: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.314: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.314: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.314: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.314: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.315: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.315: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.315: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.315: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.315: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.315: Partial capture successful. Please touch the sensor again (2/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.315: Device reported enroll progress, reported 2 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.315: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.315: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.315: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.315: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.316: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.316: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.316: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.316: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.316: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.316: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.316: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.316: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.317: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.318: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.318: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.318: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.318: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.318: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.318: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.318: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.318: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.318: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.318: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.318: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.318: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.319: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.319: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.319: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.319: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.319: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.319: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.319: Partial capture successful. Please touch the sensor again (3/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.319: Device reported enroll progress, reported 3 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.319: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.320: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.320: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.320: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.320: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.321: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.321: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.321: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.321: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.321: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.321: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.321: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.322: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.322: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.322: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.322: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.322: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.322: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.323: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.323: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.323: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.323: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.323: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.323: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.323: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.324: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.324: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.324: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.324: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.324: Response suffix valid: NO 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.324: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.324: Response suffix valid: yes 270s (process:2296): libfprint-device-DEBUG: 05:01:29.324: Device reported enroll progress, reported 3 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.324: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.324: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.324: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.324: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.325: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.326: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.326: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.326: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.326: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.326: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.326: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.326: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.326: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.327: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.327: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.327: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.327: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.327: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.327: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.328: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.328: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.328: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.328: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.328: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.328: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.328: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.329: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.329: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.329: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.329: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.329: Response suffix valid: NO 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.329: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.329: Response suffix valid: yes 270s (process:2296): libfprint-device-DEBUG: 05:01:29.329: Device reported enroll progress, reported 3 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.329: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.329: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.329: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.329: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.329: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.330: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.330: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.330: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.330: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.330: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.330: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.330: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.331: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.331: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.332: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.332: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.332: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.332: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.332: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.332: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.332: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.332: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.332: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.332: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.332: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.333: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.333: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.333: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.333: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.333: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.333: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.333: Partial capture successful. Please touch the sensor again (4/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.333: Device reported enroll progress, reported 4 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.333: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.333: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.333: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.333: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.334: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.334: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.335: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.335: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.335: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.335: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.335: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.335: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.335: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.336: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.336: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.336: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.336: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.336: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.336: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.336: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.336: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.336: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.336: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.336: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.336: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.337: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.338: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.338: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.338: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.338: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.338: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.338: Partial capture successful. Please touch the sensor again (5/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.338: Device reported enroll progress, reported 5 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.338: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.338: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.338: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.338: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.338: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.339: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.339: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.339: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.339: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.339: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.339: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.339: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.340: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.340: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.340: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.340: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.340: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.340: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.340: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.341: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.341: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.341: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.341: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.341: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.341: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.341: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.342: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.342: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.342: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.342: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.342: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.342: Partial capture successful. Please touch the sensor again (6/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.342: Device reported enroll progress, reported 6 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.342: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.342: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.342: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.342: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.343: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.343: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.343: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.343: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.343: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.343: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.343: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.343: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.344: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.344: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.344: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.344: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.344: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.344: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.344: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.345: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.345: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.345: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.345: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.345: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.345: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.345: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.346: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.346: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.346: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.346: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.346: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.346: Partial capture successful. Please touch the sensor again (7/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.346: Device reported enroll progress, reported 7 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.346: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.346: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.346: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.346: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.347: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.347: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.347: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.347: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.347: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.347: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.347: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.347: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.348: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.348: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.349: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.349: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.349: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.349: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.349: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.349: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.349: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.349: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.349: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.349: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.349: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.350: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.350: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.350: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.350: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.350: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.350: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.350: Partial capture successful. Please touch the sensor again (8/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.350: Device reported enroll progress, reported 8 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.350: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.350: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.350: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.350: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.351: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.351: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.351: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.351: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.351: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.351: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.352: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.352: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.352: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.353: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.353: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.353: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.353: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.353: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.353: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.353: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.353: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.353: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.353: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.353: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.353: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.354: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.354: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.354: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.354: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.354: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.354: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.354: Partial capture successful. Please touch the sensor again (9/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.354: Device reported enroll progress, reported 9 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.354: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.354: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.354: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.354: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.355: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.356: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.356: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.356: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.356: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.356: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.356: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.356: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.356: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.357: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.357: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.357: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.357: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.357: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.357: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.357: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.358: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.358: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.358: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.358: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.358: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.358: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.359: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.359: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.359: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.359: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.359: Response suffix valid: NO 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.359: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.359: Response suffix valid: yes 270s (process:2296): libfprint-device-DEBUG: 05:01:29.359: Device reported enroll progress, reported 9 of 10 have been completed 270s listing - device should have prints 270s clear device storage 270s clear done 270s listing - device should be empty 270s enrolling 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 1, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 2, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 3, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 4, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 4, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 5, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 6, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 7, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 8, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 9, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 10, , None, None) 270s enroll done 270s listing - device should have 1 print 270s verifying 270s verify done 270s async identifying 270s indentification_done: 270s try to enroll duplicate 270s duplicate enroll attempt done 270s listing - device should still only have 1 print 270s enroll new finger 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 1, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 1, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 2, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 3, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 4, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 5, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 6, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 7, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 8, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 9, , None, None) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))(process:2296): libfprint-SSM-DEBUG: 05:01:29.359: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.359: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.359: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.359: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.359: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.360: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.360: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.360: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.360: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.360: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.360: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.360: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.361: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.361: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.361: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.361: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.361: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.362: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.362: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.362: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.362: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.362: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.362: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.362: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.362: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.363: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.363: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.363: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.363: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.363: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.363: Response suffix valid: NO 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.363: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.363: Response suffix valid: yes 270s (process:2296): libfprint-device-DEBUG: 05:01:29.363: Device reported enroll progress, reported 9 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.363: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.363: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.363: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.363: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.364: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.364: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.365: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.365: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.365: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.365: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.365: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.365: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.365: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.366: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.366: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.366: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.366: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.366: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.366: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.366: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.366: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.366: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.366: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.366: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.366: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.367: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.367: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.367: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.367: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.367: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.367: Response suffix valid: NO 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.367: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.367: Response suffix valid: yes 270s (process:2296): libfprint-device-DEBUG: 05:01:29.367: Device reported enroll progress, reported 9 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.367: [egismoc] ENROLL_STATES entering state 8 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.367: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.367: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.367: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.368: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.369: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.369: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.369: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.369: [egismoc] ENROLL_STATES entering state 9 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.369: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.369: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.369: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.369: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.370: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.370: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.370: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.370: [egismoc] ENROLL_STATES entering state 10 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.370: Wait for finger on sensor 270s (process:2296): libfprint-device-DEBUG: 05:01:29.370: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.371: Finger on sensor callback 270s (process:2296): libfprint-device-DEBUG: 05:01:29.371: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.371: [egismoc] ENROLL_STATES entering state 11 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.371: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.371: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.371: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.371: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.372: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.372: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.372: Read capture callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.372: Response prefix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.372: Response suffix valid: yes 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.372: Partial capture successful. Please touch the sensor again (10/10) 270s (process:2296): libfprint-device-DEBUG: 05:01:29.372: Device reported enroll progress, reported 10 of 10 have been completed 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.372: [egismoc] ENROLL_STATES entering state 12 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.372: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.372: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.372: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.373: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.373: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.373: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.373: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.373: [egismoc] ENROLL_STATES entering state 13 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.373: New fingerprint ID: FP1-00000000-7-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.373: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.373: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.373: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.374: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.374: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.374: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.374: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.374: [egismoc] ENROLL_STATES entering state 14 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.374: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.374: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.374: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.375: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.376: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.376: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.376: Task SSM next state callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.376: [egismoc] ENROLL_STATES entering state 15 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.376: Enrollment was successful! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.376: Device reported enroll completion 270s (process:2296): libfprint-device-DEBUG: 05:01:29.376: Device reported finger status change: FP_FINGER_STATUS_NONE 270s (process:2296): libfprint-device-DEBUG: 05:01:29.376: Print for finger FP_FINGER_RIGHT_INDEX enrolled 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.376: [egismoc] ENROLL_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.376: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.376: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.376: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.376: List 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.376: [egismoc] LIST_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.376: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.376: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.376: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.376: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.377: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.377: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.377: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.377: Device fingerprint 1: FP1-00000000-2-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.377: Device fingerprint 2: FP1-00000000-7-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.377: Number of currently enrolled fingerprints on the device is 2 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.377: [egismoc] LIST_STATES entering state 1 270s (process:2296): libfprint-device-DEBUG: 05:01:29.377: Device reported listing completion 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.377: [egismoc] LIST_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.377: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.377: Completing action FPI_DEVICE_ACTION_LIST in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.377: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.377: Delete 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.377: [egismoc] DELETE_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.377: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.377: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.377: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.378: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.379: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.379: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.379: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.379: Device fingerprint 1: FP1-00000000-2-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.379: Device fingerprint 2: FP1-00000000-7-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.379: Number of currently enrolled fingerprints on the device is 2 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.379: [egismoc] DELETE_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.379: Get delete command 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.379: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.379: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.379: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.379: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.380: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.380: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.380: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.380: Delete callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.380: Response prefix valid: yes 270s (process:2296): libfprint-device-DEBUG: 05:01:29.380: Device reported deletion completion 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.380: [egismoc] DELETE_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.380: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.380: Completing action FPI_DEVICE_ACTION_DELETE in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.380: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.381: List 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.381: [egismoc] LIST_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.381: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.381: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.381: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.381: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.382: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.382: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.382: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.382: Device fingerprint 1: FP1-00000000-7-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.382: Number of currently enrolled fingerprints on the device is 1 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.382: [egismoc] LIST_STATES entering state 1 270s (process:2296): libfprint-device-DEBUG: 05:01:29.382: Device reported listing completion 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.382: [egismoc] LIST_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.382: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.382: Completing action FPI_DEVICE_ACTION_LIST in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.382: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.382: Clear storage 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.382: [egismoc] DELETE_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.382: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.382: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.382: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.383: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.384: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.384: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.384: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.384: Device fingerprint 1: FP1-00000000-7-00000000-nobody 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.384: Number of currently enrolled fingerprints on the device is 1 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.384: [egismoc] DELETE_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.384: Get delete command 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.384: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.384: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.384: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.384: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.385: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.385: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.385: Delete callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.385: Response prefix valid: yes 270s (process:2296): libfprint-device-DEBUG: 05:01:29.385: Device reported deletion completion 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.385: [egismoc] DELETE_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.385: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.385: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.385: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.385: List 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.385: [egismoc] LIST_STATES entering state 0 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.385: Execute command and get response 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.385: Get check bytes 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.385: [egismoc] CMD_STATES entering state 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.386: [egismoc] CMD_STATES entering state 1 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.386: Command receive callback 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.386: [egismoc] CMD_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.386: List callback 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.386: Number of currently enrolled fingerprints on the device is 0 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.386: [egismoc] LIST_STATES entering state 1 270s (process:2296): libfprint-device-DEBUG: 05:01:29.386: Device reported listing completion 270s (process:2296): libfprint-SSM-DEBUG: 05:01:29.386: [egismoc] LIST_STATES completed successfully 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.386: Task SSM done 270s (process:2296): libfprint-device-DEBUG: 05:01:29.386: Completing action FPI_DEVICE_ACTION_LIST in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.386: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.387: Closing device 270s (process:2296): libfprint-egismoc-DEBUG: 05:01:29.387: Cancel 270s (process:2296): libfprint-device-DEBUG: 05:01:29.387: Device reported close completion 270s (process:2296): libfprint-device-DEBUG: 05:01:29.387: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s (process:2296): libfprint-device-DEBUG: 05:01:29.387: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 270s finger status: 270s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xe8f98513a2c0 (FpiDeviceEgisMoc at 0xee78990)>, 10, , None, None) 270s enroll new finger done 270s listing - device should have 2 prints 270s deleting first print 270s delete done 270s listing - device should only have second print 270s clear device storage 270s clear done 270s listing - device should be empty 270s ** (umockdev-run:2292): DEBUG: 05:01:29.423: umockdev.vala:154: Removing test bed /tmp/umockdev.QO4C22 270s (umockdev-run:2292): GLib-DEBUG: 05:01:29.428: unsetenv() is not thread-safe and should not be used after threads are created 270s PASS: libfprint-2/driver-egismoc.test 270s Running test: libfprint-2/fpi-device.test 270s TAP version 14 270s # random seed: R02S8b5e5e6027ce518df3b4b1a304de77ec 270s 1..97 270s # Start of driver tests 270s ok 1 /driver/get_driver 270s ok 2 /driver/get_device_id 270s ok 3 /driver/get_name 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 4 /driver/is_open 270s ok 5 /driver/get_nr_enroll_stages 270s ok 6 /driver/set_nr_enroll_stages 270s ok 7 /driver/supports_identify 270s ok 8 /driver/supports_capture 270s ok 9 /driver/has_storage 270s ok 10 /driver/do_not_support_identify 270s ok 11 /driver/do_not_support_capture 270s ok 12 /driver/has_not_storage 270s ok 13 /driver/get_usb_device 270s ok 14 /driver/get_virtual_env 270s ok 15 /driver/get_driver_data 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 270s # 270s # libfprint-device-DEBUG: Device reported probe completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 16 /driver/initial_features 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 270s # 270s # libfprint-device-DEBUG: Device reported probe completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 17 /driver/probe 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 18 /driver/open 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 19 /driver/close 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 270s # 270s # libfprint-device-DEBUG: Device reported enroll completion 270s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 20 /driver/enroll 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 270s # 270s # libfprint-device-DEBUG: Device reported verify result 270s # libfprint-device-DEBUG: Device reported verify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 21 /driver/verify 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 270s # 270s # libfprint-device-DEBUG: Device reported identify result 270s # libfprint-device-DEBUG: Device reported identify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 22 /driver/identify 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 270s # 270s # libfprint-device-DEBUG: Device reported capture completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 23 /driver/capture 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 270s # 270s # libfprint-device-DEBUG: Device reported listing completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 24 /driver/list 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 270s # 270s # libfprint-device-DEBUG: Device reported deletion completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 25 /driver/delete 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 270s # 270s # libfprint-device-DEBUG: Device reported deletion completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 26 /driver/clear_storage 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 270s # 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 270s # 270s # libfprint-device-DEBUG: Device reported deletion completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 27 /driver/cancel 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 270s # 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 270s # 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 270s # 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 270s # 270s # libfprint-device-DEBUG: Device reported verify result 270s # libfprint-device-DEBUG: Device reported verify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 28 /driver/critical 270s ok 29 /driver/get_current_action 270s ok 30 /driver/timeout 270s ok 31 /driver/error_types 270s ok 32 /driver/retry_error_types 270s # Start of get_scan_type tests 270s ok 33 /driver/get_scan_type/press 270s ok 34 /driver/get_scan_type/swipe 270s # End of get_scan_type tests 270s # Start of set_scan_type tests 270s ok 35 /driver/set_scan_type/press 270s ok 36 /driver/set_scan_type/swipe 270s # End of set_scan_type tests 270s # Start of finger_status tests 270s ok 37 /driver/finger_status/inactive 270s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s ok 38 /driver/finger_status/waiting 270s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s ok 39 /driver/finger_status/present 270s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 270s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 270s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 270s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 270s ok 40 /driver/finger_status/changes 270s # End of finger_status tests 270s # Start of features tests 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 270s # 270s # libfprint-device-DEBUG: Device reported probe completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 41 /driver/features/probe_updates 270s # End of features tests 270s # Start of initial_features tests 270s ok 42 /driver/initial_features/none 270s ok 43 /driver/initial_features/no_capture 270s ok 44 /driver/initial_features/no_verify 270s ok 45 /driver/initial_features/no_identify 270s ok 46 /driver/initial_features/no_storage 270s ok 47 /driver/initial_features/no_list 270s ok 48 /driver/initial_features/no_delete 270s ok 49 /driver/initial_features/no_clear 270s # End of initial_features tests 270s # Start of probe tests 270s # libfprint-device-DEBUG: Device reported probe completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 50 /driver/probe/error 270s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 270s # libfprint-device-DEBUG: Device reported probe completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 51 /driver/probe/action_error 270s # End of probe tests 270s # Start of open tests 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 52 /driver/open/error 270s # End of open tests 270s # Start of close tests 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 53 /driver/close/error 270s # End of close tests 270s # Start of enroll tests 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 270s # 270s # libfprint-device-DEBUG: Device reported enroll completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 54 /driver/enroll/error 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Device reported enroll progress, reported 1758382234 of 1547071204 have been completed 270s # libfprint-device-DEBUG: Device reported enroll progress, reported 1768314218 of 1547071204 have been completed 270s # libfprint-device-DEBUG: Device reported enroll progress, reported 1912771972 of 1547071204 have been completed 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 270s # 270s # libfprint-device-DEBUG: Device reported enroll completion 270s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 55 /driver/enroll/progress 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 270s # 270s # libfprint-device-DEBUG: Device reported enroll completion 270s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 56 /driver/enroll/update_nbis 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 57 /driver/enroll/update_nbis_wrong_device 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 58 /driver/enroll/update_nbis_wrong_driver 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 59 /driver/enroll/update_nbis_missing_feature 270s # Start of error tests 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Device reported enroll completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Device reported enroll completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Device reported enroll completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 60 /driver/enroll/error/no_print 270s # End of error tests 270s # End of enroll tests 270s # Start of verify tests 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 270s # 270s # libfprint-device-DEBUG: Device reported verify result 270s # libfprint-device-DEBUG: Device reported verify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 61 /driver/verify/fail 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 270s # 270s # libfprint-device-DEBUG: Device reported verify result 270s # libfprint-device-DEBUG: Device reported verify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 62 /driver/verify/retry 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 270s # 270s # libfprint-device-DEBUG: Device reported verify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 63 /driver/verify/error 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 64 /driver/verify/not_supported 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Device reported verify result 270s # libfprint-device-DEBUG: Device reported verify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 65 /driver/verify/report_no_cb 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Device reported verify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 66 /driver/verify/not_reported 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Device reported verify result 270s # libfprint-device-DEBUG: Device reported verify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Device reported verify result 270s # libfprint-device-DEBUG: Device reported verify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Device reported verify result 270s # libfprint-device-DEBUG: Device reported verify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Device reported verify result 270s # libfprint-device-DEBUG: Device reported verify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Device reported verify result 270s # libfprint-device-DEBUG: Device reported verify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 67 /driver/verify/complete_retry 270s # End of verify tests 270s # Start of identify tests 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 270s # 270s # libfprint-device-DEBUG: Device reported identify result 270s # libfprint-device-DEBUG: Device reported identify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 68 /driver/identify/fail 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 270s # 270s # libfprint-device-DEBUG: Device reported identify result 270s # libfprint-device-DEBUG: Device reported identify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 69 /driver/identify/retry 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 270s # 270s # libfprint-device-DEBUG: Device reported identify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 270s ok 70 /driver/identify/error 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Device reported identify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 71 /driver/identify/not_reported 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Device reported identify result 270s # libfprint-device-DEBUG: Device reported identify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Device reported identify result 270s # libfprint-device-DEBUG: Device reported identify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-device-DEBUG: Device reported identify result 270s # libfprint-device-DEBUG: Device reported identify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 72 /driver/identify/complete_retry 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Device reported identify result 270s # libfprint-device-DEBUG: Device reported identify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 73 /driver/identify/report_no_cb 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 270s # 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 270s # 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 270s # 270s # libfprint-device-DEBUG: Device reported identify result 270s # libfprint-device-DEBUG: Device reported identify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 74 /driver/identify/suspend_continues 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 270s # 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 270s # 270s # libfprint-device-DEBUG: Device reported identify result 270s # libfprint-device-DEBUG: Device reported identify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 75 /driver/identify/suspend_succeeds 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 270s # 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 270s # 270s # libfprint-device-DEBUG: Device reported identify completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 270s ok 76 /driver/identify/suspend_busy_error 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 270s # 270s # libfprint-device-DEBUG: Device reported close completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s ok 77 /driver/identify/suspend_while_idle 270s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 270s # 270s # libfprint-device-DEBUG: Device reported open completion 270s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 270s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 272s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 272s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 272s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 272s # 272s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 272s # 272s # libfprint-device-DEBUG: Device reported identify completion 272s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 272s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 272s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 272s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 274s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 275s Executing: libfprint-2/fpi-device.test 277s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 277s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 277s # 277s # libfprint-device-DEBUG: Device reported close completion 277s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 277s ok 78 /driver/identify/warmup_cooldown 277s # slow test /driver/identify/warmup_cooldown executed in 7.29 secs 277s # End of identify tests 277s # Start of capture tests 277s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 277s # 277s # libfprint-device-DEBUG: Device reported open completion 277s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 277s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 277s # 277s # libfprint-device-DEBUG: Device reported close completion 277s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 277s ok 79 /driver/capture/not_supported 277s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 277s # 277s # libfprint-device-DEBUG: Device reported open completion 277s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 277s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 277s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 277s # 277s # libfprint-device-DEBUG: Device reported capture completion 277s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 277s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 277s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 277s # 277s # libfprint-device-DEBUG: Device reported close completion 277s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 277s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 277s ok 80 /driver/capture/error 277s # End of capture tests 277s # Start of list tests 277s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 277s # 277s # libfprint-device-DEBUG: Device reported open completion 277s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 277s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 277s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 277s # 277s # libfprint-device-DEBUG: Device reported listing completion 277s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 278s # 278s # libfprint-device-DEBUG: Device reported close completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s ok 81 /driver/list/error 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 278s # 278s # libfprint-device-DEBUG: Device reported open completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 278s # 278s # libfprint-device-DEBUG: Device reported close completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s ok 82 /driver/list/no_storage 278s # End of list tests 278s # Start of delete tests 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 278s # 278s # libfprint-device-DEBUG: Device reported open completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 278s # 278s # libfprint-device-DEBUG: Device reported deletion completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 278s # 278s # libfprint-device-DEBUG: Device reported close completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s ok 83 /driver/delete/error 278s # End of delete tests 278s # Start of clear_storage tests 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 278s # 278s # libfprint-device-DEBUG: Device reported open completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 278s # 278s # libfprint-device-DEBUG: Device reported deletion completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 278s # 278s # libfprint-device-DEBUG: Device reported close completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s ok 84 /driver/clear_storage/error 278s # End of clear_storage tests 278s # Start of cancel tests 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 278s # 278s # libfprint-device-DEBUG: Device reported open completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 278s # 278s # libfprint-device-DEBUG: Device reported deletion completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 278s # 278s # libfprint-device-DEBUG: Device reported close completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s ok 85 /driver/cancel/fail 278s # End of cancel tests 278s # Start of get_current_action tests 278s # libfprint-device-DEBUG: Device reported open completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 278s # 278s # libfprint-device-DEBUG: Device reported close completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s ok 86 /driver/get_current_action/open 278s # End of get_current_action tests 278s # Start of get_cancellable tests 278s ok 87 /driver/get_cancellable/error 278s # libfprint-device-DEBUG: Device reported open completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 278s # 278s # libfprint-device-DEBUG: Device reported close completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s ok 88 /driver/get_cancellable/open 278s # Start of open tests 278s # libfprint-device-DEBUG: Device reported open completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 278s # 278s # libfprint-device-DEBUG: Device reported close completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s ok 89 /driver/get_cancellable/open/internal 278s # End of open tests 278s # End of get_cancellable tests 278s # Start of action_is_cancelled tests 278s # libfprint-device-DEBUG: Device reported open completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 278s # 278s # libfprint-device-DEBUG: Device reported close completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s ok 90 /driver/action_is_cancelled/open 278s ok 91 /driver/action_is_cancelled/error 278s # Start of open tests 278s # libfprint-device-DEBUG: Device reported open completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 278s # 278s # libfprint-device-DEBUG: Device reported close completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s ok 92 /driver/action_is_cancelled/open/internal 278s # End of open tests 278s # End of action_is_cancelled tests 278s # Start of complete_action tests 278s # Start of all tests 278s ok 93 /driver/complete_action/all/error 278s # End of all tests 278s # End of complete_action tests 278s # Start of action_error tests 278s ok 94 /driver/action_error/error 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 278s # 278s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 278s # libfprint-device-DEBUG: Device reported open completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 278s # 278s # libfprint-device-DEBUG: Device reported open completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 278s # 278s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 278s # libfprint-device-DEBUG: Device reported enroll completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 278s # 278s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 278s # libfprint-device-DEBUG: Device reported verify completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 278s # 278s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 278s # libfprint-device-DEBUG: Device reported identify completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 278s # 278s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 278s # libfprint-device-DEBUG: Device reported capture completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 278s # 278s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 278s # libfprint-device-DEBUG: Device reported listing completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 278s # 278s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 278s # libfprint-device-DEBUG: Device reported deletion completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 278s # 278s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 278s # libfprint-device-DEBUG: Device reported deletion completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 278s # 278s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 278s # libfprint-device-DEBUG: Device reported close completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s ok 95 /driver/action_error/all 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 278s # 278s # libfprint-device-DEBUG: Device reported open completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 278s # 278s # libfprint-device-DEBUG: Device reported open completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 278s # 278s # libfprint-device-DEBUG: Device reported enroll completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 278s # 278s # libfprint-device-DEBUG: Device reported verify completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 278s # 278s # libfprint-device-DEBUG: Device reported identify completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 278s # 278s # libfprint-device-DEBUG: Device reported capture completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 278s # 278s # libfprint-device-DEBUG: Device reported listing completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 278s # 278s # libfprint-device-DEBUG: Device reported deletion completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 278s # 278s # libfprint-device-DEBUG: Device reported deletion completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 278s # 278s # libfprint-device-DEBUG: Device reported close completion 278s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 278s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s ok 96 /driver/action_error/fail 278s # End of action_error tests 278s # Start of timeout tests 278s ok 97 /driver/timeout/cancelled 278s # End of timeout tests 278s # End of driver tests 278s PASS: libfprint-2/fpi-device.test 278s Running test: libfprint-2/driver-elan.test 278s ** (umockdev-run:2308): DEBUG: 05:01:37.030: umockdev.vala:127: Created udev test bed /tmp/umockdev.X2KC22 278s ** (umockdev-run:2308): DEBUG: 05:01:37.030: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 278s ** (umockdev-run:2308): DEBUG: 05:01:37.032: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4/1-4.4 (subsystem usb) 278s ** (umockdev-run:2308): DEBUG: 05:01:37.034: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.X2KC22/dev/bus/usb/001/094 278s ** (umockdev-run:2308): DEBUG: 05:01:37.034: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-4 278s ** (umockdev-run:2308): DEBUG: 05:01:37.035: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-4 (subsystem usb) 278s ** (umockdev-run:2308): DEBUG: 05:01:37.037: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.X2KC22/dev/bus/usb/001/083 278s ** (umockdev-run:2308): DEBUG: 05:01:37.037: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 278s ** (umockdev-run:2308): DEBUG: 05:01:37.038: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 278s ** (umockdev-run:2308): DEBUG: 05:01:37.040: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.X2KC22/dev/bus/usb/001/001 278s ** (umockdev-run:2308): DEBUG: 05:01:37.040: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 278s ** (umockdev-run:2308): DEBUG: 05:01:37.040: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 278s (umockdev-run:2308): GLib-GIO-DEBUG: 05:01:37.042: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 278s (process:2312): libfprint-context-DEBUG: 05:01:37.154: Initializing FpContext (libfprint version 1.94.9+tod1) 278s (process:2312): libfprint-tod-DEBUG: 05:01:37.154: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 278s (process:2312): libfprint-context-DEBUG: 05:01:37.157: No driver found for USB device 17EF:1018 278s (process:2312): libfprint-context-DEBUG: 05:01:37.157: No driver found for USB device 1D6B:0002 278s (process:2312): libfprint-device-DEBUG: 05:01:37.158: Device reported probe completion 278s (process:2312): libfprint-device-DEBUG: 05:01:37.158: Completing action FPI_DEVICE_ACTION_PROBE in idle! 278s (process:2312): libfprint-device-DEBUG: 05:01:37.158: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.159: 55077890: ../libfprint/drivers/elan.c:908 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.160: Image device open completed 278s (process:2312): libfprint-device-DEBUG: 05:01:37.160: Device reported open completion 278s (process:2312): libfprint-device-DEBUG: 05:01:37.160: Completing action FPI_DEVICE_ACTION_OPEN in idle! 278s (process:2312): libfprint-device-DEBUG: 05:01:37.160: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s (process:2312): libfprint-device-DEBUG: 05:01:37.160: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.160: Activating image device 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.160: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.160: 55078992: ../libfprint/drivers/elan.c:960 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.160: 55079142: ../libfprint/drivers/elan.c:951 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.161: 55079231: ../libfprint/drivers/elan.c:892 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.161: 55079257: ../libfprint/drivers/elan.c:100 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.161: [elan] ACTIVATE_NUM_STATES entering state 0 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.161: 55079299: ../libfprint/drivers/elan.c:820 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.161: 55080030: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.161: 55080122: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.162: 55080222: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.162: 55080661: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.162: 55080773: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.162: [elan] ACTIVATE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.162: 55080825: ../libfprint/drivers/elan.c:820 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.162: FW ver 0x0140 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.162: [elan] ACTIVATE_NUM_STATES entering state 2 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.162: 55080949: ../libfprint/drivers/elan.c:820 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.163: 55081390: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.163: 55081469: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.163: 55081560: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.163: 55082046: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.163: 55082122: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.164: [elan] ACTIVATE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.164: 55082238: ../libfprint/drivers/elan.c:820 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.164: sensor dimensions, WxH: 144x64 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.164: [elan] ACTIVATE_NUM_STATES entering state 4 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.164: 55082285: ../libfprint/drivers/elan.c:820 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.164: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.164: 55082319: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.164: [elan] ACTIVATE_NUM_STATES completed successfully 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.164: 55082378: ../libfprint/drivers/elan.c:881 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.164: Image device activation completed 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.164: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.164: 55082484: ../libfprint/drivers/elan.c:960 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.164: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.164: 55082600: ../libfprint/drivers/elan.c:960 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.164: 55082616: ../libfprint/drivers/elan.c:792 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.164: 55082630: ../libfprint/drivers/elan.c:100 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.164: [elan] CALIBRATE_NUM_STATES entering state 0 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.164: 55082666: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-device-DEBUG: 05:01:37.164: Device reported finger status change: FP_FINGER_STATUS_NEEDED 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.165: 55083240: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.165: 55083250: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.165: 55083253: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.165: 55084063: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.166: 55084182: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.166: [elan] CALIBRATE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.166: 55084301: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.166: 55084305: ../libfprint/drivers/elan.c:156 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.166: 55084312: ../libfprint/drivers/elan.c:118 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.166: [elan] CALIBRATE_NUM_STATES entering state 2 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.166: 55084331: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.166: 55084915: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.166: 55084992: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.166: 55085116: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.167: 55085620: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.167: 55085701: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.167: [elan] CALIBRATE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.167: 55085772: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.167: 55085775: ../libfprint/drivers/elan.c:634 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.167: calibration mean: 8421, bg mean: 5805, delta: 2616 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.167: [elan] CALIBRATE_NUM_STATES entering state 4 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.167: 55085789: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.168: 55086578: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.168: 55086680: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.168: 55086750: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.169: 55087326: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.169: 55087436: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.169: [elan] CALIBRATE_NUM_STATES entering state 5 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.169: 55087486: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.169: calibration status: 0x01 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.219: [elan] CALIBRATE_NUM_STATES entering state 6 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.219: 55137579: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.219: [elan] CALIBRATE_NUM_STATES entering state 4 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.219: 55137594: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.220: 55138280: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.220: 55138415: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.220: 55138426: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.220: 55138995: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.221: 55139209: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.221: [elan] CALIBRATE_NUM_STATES entering state 5 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.221: 55139228: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.221: calibration status: 0x01 278s (process:2312): libfprint-device-DEBUG: 05:01:37.260: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.270: [elan] CALIBRATE_NUM_STATES entering state 6 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.270: 55189140: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.270: [elan] CALIBRATE_NUM_STATES entering state 4 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.270: 55189148: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.271: 55189808: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.271: 55189975: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.271: 55189988: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.272: 55190656: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.272: 55190778: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.272: [elan] CALIBRATE_NUM_STATES entering state 5 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.272: 55190796: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.272: calibration status: 0x01 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.322: [elan] CALIBRATE_NUM_STATES entering state 6 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.322: 55240913: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.322: [elan] CALIBRATE_NUM_STATES entering state 4 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.322: 55240928: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.323: 55241886: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.323: 55242103: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.323: 55242138: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.324: 55242869: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.324: 55243051: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.324: [elan] CALIBRATE_NUM_STATES entering state 5 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.324: 55243078: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.324: calibration status: 0x01 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.374: [elan] CALIBRATE_NUM_STATES entering state 6 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.375: 55293254: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.375: [elan] CALIBRATE_NUM_STATES entering state 4 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.375: 55293319: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.375: 55293938: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.376: 55294173: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.376: 55294190: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.376: 55294862: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.376: 55295036: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.376: [elan] CALIBRATE_NUM_STATES entering state 5 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.376: 55295066: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.376: calibration status: 0x01 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.426: [elan] CALIBRATE_NUM_STATES entering state 6 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.427: 55345246: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.427: [elan] CALIBRATE_NUM_STATES entering state 4 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.427: 55345264: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.427: 55345997: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.428: 55346197: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.428: 55346211: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.428: 55346838: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.428: 55346983: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.428: [elan] CALIBRATE_NUM_STATES entering state 5 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.428: 55347036: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.428: calibration status: 0x03 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.428: [elan] CALIBRATE_NUM_STATES entering state 0 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.428: 55347046: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.429: 55347749: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.429: 55347898: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.429: 55347909: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.430: 55348566: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.430: 55348783: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.430: [elan] CALIBRATE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.430: 55348804: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.430: 55348808: ../libfprint/drivers/elan.c:156 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.430: 55348811: ../libfprint/drivers/elan.c:118 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.430: [elan] CALIBRATE_NUM_STATES entering state 2 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.430: 55348825: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.431: 55349552: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.431: 55349700: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.431: 55349738: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.432: 55350348: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.432: 55350486: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.432: [elan] CALIBRATE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.432: 55350505: ../libfprint/drivers/elan.c:691 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.432: 55350508: ../libfprint/drivers/elan.c:634 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.432: calibration mean: 8339, bg mean: 8146, delta: 193 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.432: [elan] CALIBRATE_NUM_STATES completed successfully 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.432: 55350528: ../libfprint/drivers/elan.c:776 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.432: 55350530: ../libfprint/drivers/elan.c:620 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.432: 55350533: ../libfprint/drivers/elan.c:100 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.432: [elan] CAPTURE_NUM_STATES entering state 0 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.433: 55351182: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.433: 55351320: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.433: 55351425: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.433: skipping read, not expecting anything 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.433: 55351441: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.433: [elan] CAPTURE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.433: 55352098: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.434: 55352184: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.434: 55352195: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.434: 55352785: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.434: 55352801: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.434: [elan] CAPTURE_NUM_STATES entering state 2 278s (process:2312): libfprint-device-DEBUG: 05:01:37.434: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.434: Image device reported finger status: on 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.434: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.434: 55352834: ../libfprint/drivers/elan.c:960 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.435: 55353451: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.435: 55353589: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.435: 55353759: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.436: 55354479: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.436: 55354625: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.436: [elan] CAPTURE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.436: 55354804: ../libfprint/drivers/elan.c:203 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.436: 55354809: ../libfprint/drivers/elan.c:118 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.436: [elan] CAPTURE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.437: 55355414: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.437: 55355492: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.437: 55355502: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.438: 55356279: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.438: 55356422: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.438: [elan] CAPTURE_NUM_STATES entering state 2 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.438: Image device reported finger status: on 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.438: 55357092: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.438: 55357129: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.438: 55357135: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.439: 55357700: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.439: 55357736: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.439: [elan] CAPTURE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.439: 55357750: ../libfprint/drivers/elan.c:203 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.439: 55357761: ../libfprint/drivers/elan.c:118 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.439: [elan] CAPTURE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.440: 55358345: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.440: 55358396: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.440: 55358404: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.440: 55358913: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.440: 55359042: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.440: [elan] CAPTURE_NUM_STATES entering state 2 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.440: Image device reported finger status: on 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.441: 55359470: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.441: 55359560: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.441: 55359579: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.442: 55360172: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.442: 55360235: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.442: [elan] CAPTURE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.442: 55360326: ../libfprint/drivers/elan.c:203 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.442: 55360351: ../libfprint/drivers/elan.c:118 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.442: [elan] CAPTURE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.442: 55361012: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.442: 55361130: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.442: 55361141: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.443: 55361614: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.443: 55361737: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.443: [elan] CAPTURE_NUM_STATES entering state 2 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.443: Image device reported finger status: on 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.443: 55362160: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.444: 55362268: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.444: 55362278: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.444: 55362777: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.444: 55362828: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.444: [elan] CAPTURE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.444: 55362842: ../libfprint/drivers/elan.c:203 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.444: 55362854: ../libfprint/drivers/elan.c:118 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.444: [elan] CAPTURE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.445: 55363456: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.445: 55363517: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.445: 55363524: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.445: 55364074: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.445: 55364145: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.445: [elan] CAPTURE_NUM_STATES entering state 2 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.445: Image device reported finger status: on 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.446: 55364591: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.446: 55364605: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.446: 55364608: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.447: 55365201: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.447: 55365277: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.447: [elan] CAPTURE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.447: 55365292: ../libfprint/drivers/elan.c:203 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.447: 55365302: ../libfprint/drivers/elan.c:118 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.447: [elan] CAPTURE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.447: 55365828: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.447: 55365843: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.447: 55365846: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.448: 55366305: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.448: 55366376: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.448: [elan] CAPTURE_NUM_STATES entering state 2 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.448: Image device reported finger status: on 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.448: 55366851: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.448: 55366905: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.448: 55367040: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.449: 55367583: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.449: 55367598: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.449: [elan] CAPTURE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.449: 55367607: ../libfprint/drivers/elan.c:203 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.449: 55367619: ../libfprint/drivers/elan.c:118 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.449: [elan] CAPTURE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.449: 55368112: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.450: 55368224: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.450: 55368260: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.450: 55368698: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.450: 55368856: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.450: [elan] CAPTURE_NUM_STATES entering state 2 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.450: Image device reported finger status: on 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.451: 55369294: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.451: 55369312: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.451: 55369316: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.451: 55369835: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.451: 55369903: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.451: [elan] CAPTURE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.451: 55369917: ../libfprint/drivers/elan.c:203 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.451: 55369939: ../libfprint/drivers/elan.c:118 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.451: [elan] CAPTURE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.452: 55370459: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.452: 55370522: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.452: 55370537: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.452: 55371060: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.452: 55371121: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.452: [elan] CAPTURE_NUM_STATES entering state 2 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.452: Image device reported finger status: on 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.453: 55371579: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.453: 55371620: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.453: 55371628: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.454: 55372255: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.454: 55372311: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.454: [elan] CAPTURE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.454: 55372322: ../libfprint/drivers/elan.c:203 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.454: 55372333: ../libfprint/drivers/elan.c:118 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.454: [elan] CAPTURE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.454: 55372876: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.454: 55372923: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.454: 55372939: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.455: 55373470: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.455: 55373485: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.455: [elan] CAPTURE_NUM_STATES entering state 2 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.455: Image device reported finger status: on 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.455: 55373969: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.455: 55374033: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.455: 55374058: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.456: 55374624: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.456: 55374677: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.456: [elan] CAPTURE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.456: 55374689: ../libfprint/drivers/elan.c:203 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.456: 55374738: ../libfprint/drivers/elan.c:118 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.456: [elan] CAPTURE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.457: 55375265: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.457: 55375326: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.457: 55375342: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.457: 55375865: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.457: 55375916: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.457: [elan] CAPTURE_NUM_STATES entering state 2 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.457: Image device reported finger status: on 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.458: 55376484: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.458: 55376536: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.458: 55376544: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.458: 55377150: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.459: 55377205: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.459: [elan] CAPTURE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.459: 55377217: ../libfprint/drivers/elan.c:203 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.459: 55377228: ../libfprint/drivers/elan.c:118 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.459: [elan] CAPTURE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.459: 55377746: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.459: 55377804: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.459: 55377811: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.460: 55378292: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.460: 55378351: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.460: [elan] CAPTURE_NUM_STATES entering state 2 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.460: Image device reported finger status: on 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.460: 55378809: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.460: 55378838: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.460: 55378853: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.461: 55379382: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.461: 55379436: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.461: [elan] CAPTURE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.461: 55379447: ../libfprint/drivers/elan.c:203 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.461: 55379458: ../libfprint/drivers/elan.c:118 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.461: [elan] CAPTURE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.461: 55379965: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.461: 55380027: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.461: 55380039: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.462: 55380483: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.462: 55380527: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.462: [elan] CAPTURE_NUM_STATES entering state 2 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.462: Image device reported finger status: on 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.462: 55381032: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.462: 55381048: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.462: 55381051: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.463: 55381636: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.463: 55381650: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.463: [elan] CAPTURE_NUM_STATES entering state 3 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.463: 55381658: ../libfprint/drivers/elan.c:203 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.463: 55381669: ../libfprint/drivers/elan.c:118 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.463: [elan] CAPTURE_NUM_STATES entering state 1 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.464: 55382189: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.464: 55382252: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.464: 55382269: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.464: 55382752: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.464: 55382794: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.464: [elan] CAPTURE_NUM_STATES entering state 2 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.464: [elan] CAPTURE_NUM_STATES completed successfully 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.464: 55382815: ../libfprint/drivers/elan.c:586 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.464: 55382818: ../libfprint/drivers/elan.c:315 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.464: 55382824: ../libfprint/drivers/elan.c:272 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.465: 55383617: ../libfprint/drivers/elan.c:272 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.466: 55384388: ../libfprint/drivers/elan.c:272 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.467: 55385298: ../libfprint/drivers/elan.c:272 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.468: 55386446: ../libfprint/drivers/elan.c:272 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.469: 55387689: ../libfprint/drivers/elan.c:272 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.470: 55388964: ../libfprint/drivers/elan.c:272 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.472: 55390241: ../libfprint/drivers/elan.c:272 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.473: 55391485: ../libfprint/drivers/elan.c:272 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.474: 55392753: ../libfprint/drivers/elan.c:272 278s (process:2312): libfprint-assembling-DEBUG: 05:01:37.644: calc delta completed in 0.168203 secs 278s (process:2312): libfprint-assembling-DEBUG: 05:01:37.802: calc delta completed in 0.158678 secs 278s (process:2312): libfprint-assembling-DEBUG: 05:01:37.802: errors: 233151 rev: 207411 278s (process:2312): libfprint-assembling-DEBUG: 05:01:37.802: height is -185 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.803: Image device captured an image 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.803: 55721666: ../libfprint/drivers/elan.c:960 278s (process:2312): libfprint-device-DEBUG: 05:01:37.803: Device reported finger status change: FP_FINGER_STATUS_PRESENT 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.803: 55721730: ../libfprint/drivers/elan.c:507 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.803: 55721746: ../libfprint/drivers/elan.c:100 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.803: [elan] STOP_CAPTURE_NUM_STATES entering state 0 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.803: 55721786: ../libfprint/drivers/elan.c:466 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.805: 55723542: ../libfprint/drivers/elan.c:346 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.805: 55723606: ../libfprint/drivers/elan.c:366 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.805: 55723623: ../libfprint/drivers/elan.c:379 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.805: skipping read, not expecting anything 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.805: 55723657: ../libfprint/drivers/elan.c:335 278s (process:2312): libfprint-SSM-DEBUG: 05:01:37.805: [elan] STOP_CAPTURE_NUM_STATES completed successfully 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.805: 55723691: ../libfprint/drivers/elan.c:483 278s (process:2312): libfprint-device-DEBUG: 05:01:37.805: Device reported finger status change: FP_FINGER_STATUS_NONE 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.805: Image device reported finger status: off 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.805: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.805: 55723854: ../libfprint/drivers/elan.c:960 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.805: Deactivating image device 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.805: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.805: 55723911: ../libfprint/drivers/elan.c:960 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.805: 55723930: ../libfprint/drivers/elan.c:975 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.805: Image device deactivation completed 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.805: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.805: 55724047: ../libfprint/drivers/elan.c:960 278s (process:2312): libfprint-image-DEBUG: 05:01:37.821: Minutiae scan completed in 0.018155 secs 278s (process:2312): libfprint-device-DEBUG: 05:01:37.821: Device reported capture completion 278s (process:2312): libfprint-device-DEBUG: 05:01:37.821: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 278s (process:2312): libfprint-device-DEBUG: 05:01:37.821: Updated temperature model after 0.56 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.822: 55740294: ../libfprint/drivers/elan.c:939 278s (process:2312): libfprint-elan-DEBUG: 05:01:37.822: 55740302: ../libfprint/drivers/elan.c:100 278s (process:2312): libfprint-image_device-DEBUG: 05:01:37.822: Image device close completed 278s (process:2312): libfprint-device-DEBUG: 05:01:37.822: Device reported close completion 278s (process:2312): libfprint-device-DEBUG: 05:01:37.822: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 278s (process:2312): libfprint-device-DEBUG: 05:01:37.822: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 278s ** (umockdev-run:2308): DEBUG: 05:01:37.922: umockdev.vala:154: Removing test bed /tmp/umockdev.X2KC22 278s (umockdev-run:2308): GLib-DEBUG: 05:01:37.926: unsetenv() is not thread-safe and should not be used after threads are created 278s Comparing PNGs /tmp/libfprint-umockdev-test-4c8y8bi4/capture.png and /usr/share/installed-tests/libfprint-2/elan/capture.png 278s PASS: libfprint-2/driver-elan.test 278s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 279s TAP version 14 279s # random seed: R02Sa94e238c3c3ca84033a6ff65c691b3d7 279s 1..97 279s # Start of driver tests 279s ok 1 /driver/get_driver 279s ok 2 /driver/get_device_id 279s ok 3 /driver/get_name 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 4 /driver/is_open 279s ok 5 /driver/get_nr_enroll_stages 279s ok 6 /driver/set_nr_enroll_stages 279s ok 7 /driver/supports_identify 279s ok 8 /driver/supports_capture 279s ok 9 /driver/has_storage 279s ok 10 /driver/do_not_support_identify 279s ok 11 /driver/do_not_support_capture 279s ok 12 /driver/has_not_storage 279s ok 13 /driver/get_usb_device 279s ok 14 /driver/get_virtual_env 279s ok 15 /driver/get_driver_data 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 279s # 279s # libfprint-device-DEBUG: Device reported probe completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s ok 16 /driver/initial_features 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE 279s # 279s # libfprint-device-DEBUG: Device reported probe completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 17 /driver/probe 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 18 /driver/open 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 19 /driver/close 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 279s # 279s # libfprint-device-DEBUG: Device reported enroll completion 279s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 20 /driver/enroll 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 279s # 279s # libfprint-device-DEBUG: Device reported verify result 279s # libfprint-device-DEBUG: Device reported verify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 21 /driver/verify 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 279s # 279s # libfprint-device-DEBUG: Device reported identify result 279s # libfprint-device-DEBUG: Device reported identify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 22 /driver/identify 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 279s # 279s # libfprint-device-DEBUG: Device reported capture completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 23 /driver/capture 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 279s # 279s # libfprint-device-DEBUG: Device reported listing completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 24 /driver/list 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 279s # 279s # libfprint-device-DEBUG: Device reported deletion completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 25 /driver/delete 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 279s # 279s # libfprint-device-DEBUG: Device reported deletion completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 26 /driver/clear_storage 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 279s # 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 279s # 279s # libfprint-device-DEBUG: Device reported deletion completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 27 /driver/cancel 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 279s # 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 279s # 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 279s # 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 279s # 279s # libfprint-device-DEBUG: Device reported verify result 279s # libfprint-device-DEBUG: Device reported verify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 28 /driver/critical 279s ok 29 /driver/get_current_action 279s ok 30 /driver/timeout 279s ok 31 /driver/error_types 279s ok 32 /driver/retry_error_types 279s # Start of get_scan_type tests 279s ok 33 /driver/get_scan_type/press 279s ok 34 /driver/get_scan_type/swipe 279s # End of get_scan_type tests 279s # Start of set_scan_type tests 279s ok 35 /driver/set_scan_type/press 279s ok 36 /driver/set_scan_type/swipe 279s # End of set_scan_type tests 279s # Start of finger_status tests 279s ok 37 /driver/finger_status/inactive 279s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 279s ok 38 /driver/finger_status/waiting 279s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 279s ok 39 /driver/finger_status/present 279s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 279s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 279s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT 279s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 279s ok 40 /driver/finger_status/changes 279s # End of finger_status tests 279s # Start of features tests 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 279s # 279s # libfprint-device-DEBUG: Device reported probe completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 41 /driver/features/probe_updates 279s # End of features tests 279s # Start of initial_features tests 279s ok 42 /driver/initial_features/none 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s ok 43 /driver/initial_features/no_capture 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s ok 44 /driver/initial_features/no_verify 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s ok 45 /driver/initial_features/no_identify 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s ok 46 /driver/initial_features/no_storage 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s ok 47 /driver/initial_features/no_list 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s ok 48 /driver/initial_features/no_delete 279s ok 49 /driver/initial_features/no_clear 279s # End of initial_features tests 279s # Start of probe tests 279s # libfprint-device-DEBUG: Device reported probe completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 50 /driver/probe/error 279s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE 279s # libfprint-device-DEBUG: Device reported probe completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 51 /driver/probe/action_error 279s # End of probe tests 279s # Start of open tests 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 52 /driver/open/error 279s # End of open tests 279s # Start of close tests 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 53 /driver/close/error 279s # End of close tests 279s # Start of enroll tests 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 279s # 279s # libfprint-device-DEBUG: Device reported enroll completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 54 /driver/enroll/error 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Device reported enroll progress, reported 1209383868 of 841851401 have been completed 279s # libfprint-device-DEBUG: Device reported enroll progress, reported 1563111168 of 841851401 have been completed 279s # libfprint-device-DEBUG: Device reported enroll progress, reported 1618082818 of 841851401 have been completed 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 279s # 279s # libfprint-device-DEBUG: Device reported enroll completion 279s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 55 /driver/enroll/progress 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 279s # 279s # libfprint-device-DEBUG: Device reported enroll completion 279s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 56 /driver/enroll/update_nbis 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 57 /driver/enroll/update_nbis_wrong_device 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 58 /driver/enroll/update_nbis_wrong_driver 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 59 /driver/enroll/update_nbis_missing_feature 279s # Start of error tests 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Device reported enroll completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Device reported enroll completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Device reported enroll completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 60 /driver/enroll/error/no_print 279s # End of error tests 279s # End of enroll tests 279s # Start of verify tests 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 279s # 279s # libfprint-device-DEBUG: Device reported verify result 279s # libfprint-device-DEBUG: Device reported verify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 61 /driver/verify/fail 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 279s # 279s # libfprint-device-DEBUG: Device reported verify result 279s # libfprint-device-DEBUG: Device reported verify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 62 /driver/verify/retry 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 279s # 279s # libfprint-device-DEBUG: Device reported verify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 63 /driver/verify/error 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 64 /driver/verify/not_supported 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Device reported verify result 279s # libfprint-device-DEBUG: Device reported verify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 65 /driver/verify/report_no_cb 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Device reported verify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 66 /driver/verify/not_reported 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Device reported verify result 279s # libfprint-device-DEBUG: Device reported verify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Device reported verify result 279s # libfprint-device-DEBUG: Device reported verify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Device reported verify result 279s # libfprint-device-DEBUG: Device reported verify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Device reported verify result 279s # libfprint-device-DEBUG: Device reported verify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Device reported verify result 279s # libfprint-device-DEBUG: Device reported verify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 67 /driver/verify/complete_retry 279s # End of verify tests 279s # Start of identify tests 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 279s # 279s # libfprint-device-DEBUG: Device reported identify result 279s # libfprint-device-DEBUG: Device reported identify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 68 /driver/identify/fail 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 279s # 279s # libfprint-device-DEBUG: Device reported identify result 279s # libfprint-device-DEBUG: Device reported identify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 69 /driver/identify/retry 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 279s # 279s # libfprint-device-DEBUG: Device reported identify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 70 /driver/identify/error 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Device reported identify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 279s ok 71 /driver/identify/not_reported 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Device reported identify result 279s # libfprint-device-DEBUG: Device reported identify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Device reported identify result 279s # libfprint-device-DEBUG: Device reported identify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-device-DEBUG: Device reported identify result 279s # libfprint-device-DEBUG: Device reported identify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 72 /driver/identify/complete_retry 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Device reported identify result 279s # libfprint-device-DEBUG: Device reported identify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 73 /driver/identify/report_no_cb 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 279s # 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 279s # 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 279s # 279s # libfprint-device-DEBUG: Device reported identify result 279s # libfprint-device-DEBUG: Device reported identify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 74 /driver/identify/suspend_continues 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 279s # 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 279s # 279s # libfprint-device-DEBUG: Device reported identify result 279s # libfprint-device-DEBUG: Device reported identify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 75 /driver/identify/suspend_succeeds 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 279s # 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 279s # 279s # libfprint-device-DEBUG: Device reported identify completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 279s ok 76 /driver/identify/suspend_busy_error 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 279s # 279s # libfprint-device-DEBUG: Device reported close completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s ok 77 /driver/identify/suspend_while_idle 279s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 279s # libfprint-device-DEBUG: Tod version info is 'current' 279s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 279s # 279s # libfprint-device-DEBUG: Device reported open completion 279s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 279s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 280s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 281s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT 281s # libfprint-device-DEBUG: Idle cancelling on ongoing operation! 281s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 281s # 281s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 281s # 281s # libfprint-device-DEBUG: Device reported identify completion 281s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 281s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 281s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 281s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT 283s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM 285s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 286s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s ok 78 /driver/identify/warmup_cooldown 286s # slow test /driver/identify/warmup_cooldown executed in 7.30 secs 286s # End of identify tests 286s # Start of capture tests 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 286s # 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s ok 79 /driver/capture/not_supported 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 286s # 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 286s # 286s # libfprint-device-DEBUG: Device reported capture completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s ok 80 /driver/capture/error 286s # End of capture tests 286s # Start of list tests 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 286s # 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 286s # 286s # libfprint-device-DEBUG: Device reported listing completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s ok 81 /driver/list/error 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 286s # 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s ok 82 /driver/list/no_storage 286s # End of list tests 286s # Start of delete tests 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 286s # 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 286s # 286s # libfprint-device-DEBUG: Device reported deletion completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s ok 83 /driver/delete/error 286s # End of delete tests 286s # Start of clear_storage tests 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 286s # 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 286s # libfprint-device-DEBUG: Tod version info is 'current' 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 286s # 286s # libfprint-device-DEBUG: Device reported deletion completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s ok 84 /driver/clear_storage/error 286s # End of clear_storage tests 286s # Start of cancel tests 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 286s # 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 286s # 286s # libfprint-device-DEBUG: Device reported deletion completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s ok 85 /driver/cancel/fail 286s # End of cancel tests 286s # Start of get_current_action tests 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s ok 86 /driver/get_current_action/open 286s # End of get_current_action tests 286s # Start of get_cancellable tests 286s ok 87 /driver/get_cancellable/error 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s ok 88 /driver/get_cancellable/open 286s # Start of open tests 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s ok 89 /driver/get_cancellable/open/internal 286s # End of open tests 286s # End of get_cancellable tests 286s # Start of action_is_cancelled tests 286s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 286s # libfprint-device-DEBUG: Tod version info is 'current' 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s ok 90 /driver/action_is_cancelled/open 286s ok 91 /driver/action_is_cancelled/error 286s # Start of open tests 286s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 286s # libfprint-device-DEBUG: Tod version info is 'current' 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s ok 92 /driver/action_is_cancelled/open/internal 286s # End of open tests 286s # End of action_is_cancelled tests 286s # Start of complete_action tests 286s # Start of all tests 286s ok 93 /driver/complete_action/all/error 286s # End of all tests 286s # End of complete_action tests 286s # Start of action_error tests 286s ok 94 /driver/action_error/error 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 286s # 286s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 286s # 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 286s # 286s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL 286s # libfprint-device-DEBUG: Device reported enroll completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 286s # 286s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY 286s # libfprint-device-DEBUG: Device reported verify completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 286s # 286s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 286s # libfprint-device-DEBUG: Device reported identify completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 286s # 286s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE 286s # libfprint-device-DEBUG: Device reported capture completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 286s # 286s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST 286s # libfprint-device-DEBUG: Device reported listing completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 286s # 286s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE 286s # libfprint-device-DEBUG: Device reported deletion completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 286s # libfprint-device-DEBUG: Tod version info is 'current' 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 286s # 286s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE 286s # libfprint-device-DEBUG: Device reported deletion completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s ok 95 /driver/action_error/all 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 286s # 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 286s # 286s # libfprint-device-DEBUG: Device reported open completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL 286s # 286s # libfprint-device-DEBUG: Device reported enroll completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY 286s # 286s # libfprint-device-DEBUG: Device reported verify completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY 286s # 286s # libfprint-device-DEBUG: Device reported identify completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE 286s # 286s # libfprint-device-DEBUG: Device reported capture completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST 286s # 286s # libfprint-device-DEBUG: Device reported listing completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE 286s # 286s # libfprint-device-DEBUG: Device reported deletion completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current' 286s # libfprint-device-DEBUG: Tod version info is 'current' 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE 286s # 286s # libfprint-device-DEBUG: Device reported deletion completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 286s # 286s # libfprint-device-DEBUG: Device reported close completion 286s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 286s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 286s ok 96 /driver/action_error/fail 286s # End of action_error tests 286s # Start of timeout tests 286s ok 97 /driver/timeout/cancelled 286s # End of timeout tests 286s # End of driver tests 286s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test 286s Running test: libfprint-2/driver-vfs0050.test 286s ** (umockdev-run:2327): DEBUG: 05:01:45.618: umockdev.vala:127: Created udev test bed /tmp/umockdev.3OZZ12 286s ** (umockdev-run:2327): DEBUG: 05:01:45.619: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 286s ** (umockdev-run:2327): DEBUG: 05:01:45.620: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 286s ** (umockdev-run:2327): DEBUG: 05:01:45.623: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3OZZ12/dev/bus/usb/001/004 286s ** (umockdev-run:2327): DEBUG: 05:01:45.623: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 286s ** (umockdev-run:2327): DEBUG: 05:01:45.624: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 286s ** (umockdev-run:2327): DEBUG: 05:01:45.626: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3OZZ12/dev/bus/usb/001/001 286s ** (umockdev-run:2327): DEBUG: 05:01:45.627: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 286s ** (umockdev-run:2327): DEBUG: 05:01:45.627: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 286s (umockdev-run:2327): GLib-GIO-DEBUG: 05:01:45.629: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 286s (process:2331): libfprint-context-DEBUG: 05:01:45.911: Initializing FpContext (libfprint version 1.94.9+tod1) 286s (process:2331): libfprint-tod-DEBUG: 05:01:45.911: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 286s (process:2331): libfprint-context-DEBUG: 05:01:45.916: No driver found for USB device 1D6B:0002 286s (process:2331): libfprint-device-DEBUG: 05:01:45.917: Device reported probe completion 286s (process:2331): libfprint-device-DEBUG: 05:01:45.917: Completing action FPI_DEVICE_ACTION_PROBE in idle! 286s (process:2331): libfprint-device-DEBUG: 05:01:45.917: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.922: [vfs0050] SSM_STATES entering state 0 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.924: [vfs0050] SSM_STATES entering state 1 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.927: [vfs0050] SSM_STATES entering state 2 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.929: [vfs0050] SSM_STATES entering state 3 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.929: [vfs0050] SUBSM1_STATES entering state 0 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.930: [vfs0050] SUBSM1_STATES entering state 1 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.931: [vfs0050] SUBSM1_STATES entering state 2 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.933: [vfs0050] SUBSM1_STATES completed successfully 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.933: [vfs0050] SSM_STATES entering state 4 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.933: [vfs0050] SUBSM2_STATES entering state 0 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.934: [vfs0050] SUBSM2_STATES entering state 1 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.935: [vfs0050] SUBSM2_STATES entering state 2 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.937: [vfs0050] SUBSM2_STATES entering state 3 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.938: [vfs0050] SUBSM2_STATES entering state 4 286s (process:2331): libfprint-SSM-DEBUG: 05:01:45.939: [vfs0050] SUBSM2_STATES entering state 5 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.940: [vfs0050] SUBSM2_STATES entering state 6 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.940: [vfs0050] SUBSM1_STATES entering state 0 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.941: [vfs0050] SUBSM1_STATES entering state 1 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.942: [vfs0050] SUBSM1_STATES entering state 2 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.944: [vfs0050] SUBSM1_STATES completed successfully 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.944: [vfs0050] SUBSM2_STATES completed successfully 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.944: [vfs0050] SSM_STATES entering state 5 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.944: [vfs0050] SSM_STATES completed successfully 287s (process:2331): libfprint-image_device-DEBUG: 05:01:45.944: Image device open completed 287s (process:2331): libfprint-device-DEBUG: 05:01:45.944: Device reported open completion 287s (process:2331): libfprint-device-DEBUG: 05:01:45.944: Completing action FPI_DEVICE_ACTION_OPEN in idle! 287s (process:2331): libfprint-device-DEBUG: 05:01:45.944: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s (process:2331): libfprint-device-DEBUG: 05:01:45.945: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s (process:2331): libfprint-image_device-DEBUG: 05:01:45.945: Activating image device 287s (process:2331): libfprint-image_device-DEBUG: 05:01:45.945: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.945: [vfs0050] SSM_STATES entering state 0 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.946: [vfs0050] SSM_STATES entering state 1 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.947: [vfs0050] SSM_STATES entering state 2 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.948: [vfs0050] SSM_STATES entering state 3 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.948: [vfs0050] SUBSM1_STATES entering state 0 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.948: [vfs0050] SUBSM1_STATES entering state 1 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.949: [vfs0050] SUBSM1_STATES entering state 2 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.950: [vfs0050] SUBSM1_STATES completed successfully 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.950: [vfs0050] SSM_STATES entering state 4 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.950: [vfs0050] SUBSM2_STATES entering state 0 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.951: [vfs0050] SUBSM2_STATES entering state 1 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.952: [vfs0050] SUBSM2_STATES entering state 2 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.953: [vfs0050] SUBSM2_STATES entering state 3 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.954: [vfs0050] SUBSM2_STATES entering state 4 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.954: [vfs0050] SUBSM2_STATES entering state 5 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.956: [vfs0050] SUBSM2_STATES entering state 6 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.956: [vfs0050] SUBSM1_STATES entering state 0 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.957: [vfs0050] SUBSM1_STATES entering state 1 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.957: [vfs0050] SUBSM1_STATES entering state 2 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.958: [vfs0050] SUBSM1_STATES completed successfully 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.958: [vfs0050] SUBSM2_STATES completed successfully 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.958: [vfs0050] SSM_STATES entering state 5 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.958: [vfs0050] SUBSM2_STATES entering state 0 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.959: [vfs0050] SUBSM2_STATES entering state 1 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.960: [vfs0050] SUBSM2_STATES entering state 2 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.960: [vfs0050] SUBSM2_STATES entering state 3 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.961: [vfs0050] SUBSM2_STATES entering state 4 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.962: [vfs0050] SUBSM2_STATES entering state 5 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.963: [vfs0050] SUBSM2_STATES entering state 6 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.963: [vfs0050] SUBSM2_STATES completed successfully 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.963: [vfs0050] SSM_STATES entering state 6 287s (process:2331): libfprint-image_device-DEBUG: 05:01:45.963: Image device activation completed 287s (process:2331): libfprint-image_device-DEBUG: 05:01:45.963: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 287s (process:2331): libfprint-image_device-DEBUG: 05:01:45.963: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 287s (process:2331): libfprint-device-DEBUG: 05:01:45.963: Device reported finger status change: FP_FINGER_STATUS_NEEDED 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.963: [vfs0050] SSM_STATES entering state 7 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.964: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-device-DEBUG: 05:01:45.964: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 287s (process:2331): libfprint-image_device-DEBUG: 05:01:45.964: Image device reported finger status: on 287s (process:2331): libfprint-image_device-DEBUG: 05:01:45.964: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.965: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.966: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.967: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.968: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.969: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.970: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.971: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.972: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.973: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.974: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.975: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.976: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.978: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.979: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.980: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.981: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.982: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.983: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.984: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.985: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.986: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.987: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.988: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.990: [vfs0050] SSM_STATES entering state 8 287s (process:2331): libfprint-SSM-DEBUG: 05:01:45.991: [vfs0050] SSM_STATES entering state 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 1740200505991716 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 1 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 1 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 2 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 1 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 5 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 3 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 1 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 8 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 2 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 5 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 3 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 1 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 8 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.991: 4 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 2 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 8 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 4 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 94 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 90 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 95 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 93 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 94 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 90 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 88 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 86 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 84 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 64 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 8 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 4 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 2 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 8 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 4 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 2 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 3 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 94 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 94 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 90 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 88 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 86 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 84 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 95 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 93 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 95 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 93 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 91 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 89 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 87 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 85 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 83 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 87 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 85 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 83 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 81 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 79 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 81 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 79 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 77 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 79 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 77 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 75 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 79 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 75 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 79 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 77 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 75 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 69 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 64 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 64 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 62 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 60 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 58 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 60 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 62 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 58 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 56 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 56 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 58 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 56 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 48 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 49 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 49 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 48 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 49 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 45 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.992: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 39 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 39 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 37 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.993: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 1 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 91 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 89 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 86 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 60 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 60 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 62 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 56 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.994: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 93 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.995: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 75 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 74 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 37 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.996: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 84 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 45 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 79 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 67 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 83 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 69 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 67 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 90 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 79 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 67 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 89 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 87 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 90 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 88 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 86 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 37 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 75 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 76 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 74 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 39 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 48 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 64 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 62 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 83 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 86 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 76 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 8 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 4 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.997: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 90 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 95 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 94 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 83 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 81 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 89 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 87 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 81 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 77 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 49 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 45 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 37 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 3 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 77 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 85 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 60 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 58 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 4 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 63 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 69 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 74 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 93 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 83 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 81 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 48 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 77 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 39 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 93 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 85 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 83 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 86 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 4 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 77 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 80 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 74 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 72 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 45 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 3 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 37 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 60 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 56 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 56 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 58 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 62 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 8 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 4 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 93 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 93 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 89 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 91 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.998: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 69 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 69 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 4 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 2 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 86 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 87 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 1 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 39 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 89 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 3 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 39 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 89 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 75 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 81 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 75 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 62 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 94 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 56 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 91 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 93 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 89 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 76 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 72 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 3 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 83 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 49 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 5 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 3 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 4 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 37 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 81 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 88 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 88 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 89 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 75 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 3 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 80 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 67 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 76 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 74 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 79 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 77 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 1 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 45 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 84 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 5 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 83 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 81 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 74 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 1 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 75 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 69 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 67 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:45.999: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 100 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 1 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 95 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 88 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 86 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 5 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 93 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 75 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 81 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 77 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 67 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 69 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 67 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 63 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 84 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 95 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 84 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 45 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 39 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 58 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 63 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 49 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 5 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 1 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 37 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 5 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 3 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 8 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 1 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 4 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 4 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 2 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 1 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 2 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 4 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 2 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.000: 1 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: offsets_filtered: 1740200506002287 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 5 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 5 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 8 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 8 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 90 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 94 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 95 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 94 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 93 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 90 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 88 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 86 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 84 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.002: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 99 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 98 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 97 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 96 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 95 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 95 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 94 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 94 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 93 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 93 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 91 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 90 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 89 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 88 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 87 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 87 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 86 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 85 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 85 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 84 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 83 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 83 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 81 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 81 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 79 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 79 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 79 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 79 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 79 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 77 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 77 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 77 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 75 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 75 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 75 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 69 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 64 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 64 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 62 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 62 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 60 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 60 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 58 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 58 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 56 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 56 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 56 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 49 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 49 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 49 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 49 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 48 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 45 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 39 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 39 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 37 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.003: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.004: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 30 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.005: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 19 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 18 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 16 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.006: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 11 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 12 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 67 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 67 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 69 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 67 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 67 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 64 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 64 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 62 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 48 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 81 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 83 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 90 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 94 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 94 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 94 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 94 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 92 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 90 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 89 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 87 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 83 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 81 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 81 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 77 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 70 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 49 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 45 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 37 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 20 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 24 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.007: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 58 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 58 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 58 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 58 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 60 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 60 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 60 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 60 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 54 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 45 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 43 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 42 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 36 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 47 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 46 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 32 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 26 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 23 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 25 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 39 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 39 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 39 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 39 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 62 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 62 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 62 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 62 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 56 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 56 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 56 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 49 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 44 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 37 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 37 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 37 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 37 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 37 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 38 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 45 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.008: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 52 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 67 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 73 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 71 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 69 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 68 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 67 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 66 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 61 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 59 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 57 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 51 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 33 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 34 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 63 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 63 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 63 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 63 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 65 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 63 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 58 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 58 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 55 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 50 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 53 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 45 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 45 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 41 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 40 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 39 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 35 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 31 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 29 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 28 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 27 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 22 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 21 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 17 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 15 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 14 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 13 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 10 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 9 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 8 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 7 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 4 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 6 287s (process:2331): libfprint-assembling-DEBUG: 05:01:46.009: 1 287s (process:2331): libfprint-image_device-DEBUG: 05:01:46.011: Image device captured an image 287s (process:2331): libfprint-image_device-DEBUG: 05:01:46.012: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 287s (process:2331): libfprint-device-DEBUG: 05:01:46.012: Device reported finger status change: FP_FINGER_STATUS_PRESENT 287s (process:2331): libfprint-device-DEBUG: 05:01:46.012: Device reported finger status change: FP_FINGER_STATUS_NONE 287s (process:2331): libfprint-image_device-DEBUG: 05:01:46.012: Image device reported finger status: off 287s (process:2331): libfprint-image_device-DEBUG: 05:01:46.012: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 287s (process:2331): libfprint-image_device-DEBUG: 05:01:46.012: Deactivating image device 287s (process:2331): libfprint-image_device-DEBUG: 05:01:46.012: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 287s (process:2331): libfprint-device-DEBUG: 05:01:46.047: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 287s (process:2331): libfprint-image-DEBUG: 05:01:46.048: Minutiae scan completed in 0.035686 secs 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.091: [vfs0050] SSM_STATES entering state 10 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.091: [vfs0050] SSM_STATES entering state 3 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.091: [vfs0050] SUBSM1_STATES entering state 0 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.091: [vfs0050] SUBSM1_STATES entering state 1 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.092: [vfs0050] SUBSM1_STATES entering state 2 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.093: [vfs0050] SUBSM1_STATES completed successfully 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.093: [vfs0050] SSM_STATES entering state 4 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.093: [vfs0050] SUBSM2_STATES entering state 0 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.093: [vfs0050] SUBSM2_STATES entering state 1 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.094: [vfs0050] SUBSM2_STATES entering state 2 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.095: [vfs0050] SUBSM2_STATES entering state 3 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.096: [vfs0050] SUBSM2_STATES entering state 4 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.097: [vfs0050] SUBSM2_STATES entering state 5 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.098: [vfs0050] SUBSM2_STATES entering state 6 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.098: [vfs0050] SUBSM1_STATES entering state 0 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.099: [vfs0050] SUBSM1_STATES entering state 1 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.100: [vfs0050] SUBSM1_STATES entering state 2 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.101: [vfs0050] SUBSM1_STATES completed successfully 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.101: [vfs0050] SUBSM2_STATES completed successfully 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.101: [vfs0050] SSM_STATES entering state 5 287s (process:2331): libfprint-SSM-DEBUG: 05:01:46.101: [vfs0050] SSM_STATES completed successfully 287s (process:2331): libfprint-image_device-DEBUG: 05:01:46.101: Image device deactivation completed 287s (process:2331): libfprint-image_device-DEBUG: 05:01:46.101: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 287s (process:2331): libfprint-device-DEBUG: 05:01:46.101: Device reported capture completion 287s (process:2331): libfprint-device-DEBUG: 05:01:46.101: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 287s (process:2331): libfprint-device-DEBUG: 05:01:46.101: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 287s (process:2331): libfprint-image_device-DEBUG: 05:01:46.101: Image device close completed 287s (process:2331): libfprint-device-DEBUG: 05:01:46.101: Device reported close completion 287s (process:2331): libfprint-device-DEBUG: 05:01:46.102: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 287s (process:2331): libfprint-device-DEBUG: 05:01:46.102: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 287s ** (umockdev-run:2327): DEBUG: 05:01:46.296: umockdev.vala:154: Removing test bed /tmp/umockdev.3OZZ12 287s (umockdev-run:2327): GLib-DEBUG: 05:01:46.300: unsetenv() is not thread-safe and should not be used after threads are created 287s Comparing PNGs /tmp/libfprint-umockdev-test-ni0fwhbn/capture.png and /usr/share/installed-tests/libfprint-2/vfs0050/capture.png 287s PASS: libfprint-2/driver-vfs0050.test 287s Running test: libfprint-2/fp-device.test 287s TAP version 14 287s # random seed: R02S6a4997c946152cb8d67640da0d970fdb 287s 1..17 287s # Start of device tests 287s # Start of async tests 287s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 287s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 287s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 287s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 287s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 287s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-QFSG22/virtual_image.socket 287s # libfprint-context-DEBUG: created 287s # libfprint-device-DEBUG: Device reported probe completion 287s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 287s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:46.361: 64279976: ../libfprint/drivers/virtual-image.c:216 287s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:46.361: 64280094: ../libfprint/drivers/virtual-device-listener.c:153 287s # libfprint-image_device-DEBUG: Image device open completed 287s # libfprint-device-DEBUG: Device reported open completion 287s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 287s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:46.462: 64380919: ../libfprint/drivers/virtual-image.c:244 287s # libfprint-image_device-DEBUG: Image device close completed 287s # libfprint-device-DEBUG: Device reported close completion 287s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 287s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 287s ok 1 /device/async/open 287s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 287s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 287s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 287s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 287s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 287s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 287s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-SF6112/virtual_image.socket 287s # libfprint-context-DEBUG: created 287s # libfprint-device-DEBUG: Device reported probe completion 287s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 287s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:46.569: 64487314: ../libfprint/drivers/virtual-image.c:216 287s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:46.569: 64487379: ../libfprint/drivers/virtual-device-listener.c:153 287s # libfprint-image_device-DEBUG: Image device open completed 287s # libfprint-device-DEBUG: Device reported open completion 287s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 287s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:46.670: 64588283: ../libfprint/drivers/virtual-image.c:244 287s # libfprint-image_device-DEBUG: Image device close completed 287s # libfprint-device-DEBUG: Device reported close completion 287s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 287s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 287s ok 2 /device/async/close 287s # End of async tests 287s # Start of sync tests 287s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 287s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 287s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 287s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 287s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 287s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 287s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-1YC312/virtual_image.socket 287s # libfprint-context-DEBUG: created 287s # libfprint-device-DEBUG: Device reported probe completion 287s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 287s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:46.777: 64695320: ../libfprint/drivers/virtual-image.c:216 287s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:46.777: 64695378: ../libfprint/drivers/virtual-device-listener.c:153 287s # libfprint-image_device-DEBUG: Image device open completed 287s # libfprint-device-DEBUG: Device reported open completion 287s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 287s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 287s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:46.878: 64796303: ../libfprint/drivers/virtual-image.c:244 288s # libfprint-image_device-DEBUG: Image device close completed 288s # libfprint-device-DEBUG: Device reported close completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 288s ok 3 /device/sync/open 288s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 288s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 288s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 288s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 288s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 288s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 288s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-F2GA22/virtual_image.socket 288s # libfprint-context-DEBUG: created 288s # libfprint-device-DEBUG: Device reported probe completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:46.985: 64903255: ../libfprint/drivers/virtual-image.c:216 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:46.985: 64903313: ../libfprint/drivers/virtual-device-listener.c:153 288s # libfprint-image_device-DEBUG: Image device open completed 288s # libfprint-device-DEBUG: Device reported open completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:47.086: 65004206: ../libfprint/drivers/virtual-image.c:244 288s # libfprint-image_device-DEBUG: Image device close completed 288s # libfprint-device-DEBUG: Device reported close completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 288s ok 4 /device/sync/close 288s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 288s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 288s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 288s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 288s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 288s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 288s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-9JVF22/virtual_image.socket 288s # libfprint-context-DEBUG: created 288s # libfprint-device-DEBUG: Device reported probe completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:47.192: 65110563: ../libfprint/drivers/virtual-image.c:216 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:47.192: 65110637: ../libfprint/drivers/virtual-device-listener.c:153 288s # libfprint-image_device-DEBUG: Image device open completed 288s # libfprint-device-DEBUG: Device reported open completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:47.293: 65211374: ../libfprint/drivers/virtual-image.c:244 288s # libfprint-image_device-DEBUG: Image device close completed 288s # libfprint-device-DEBUG: Device reported close completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 288s ok 5 /device/sync/get_driver 288s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 288s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 288s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 288s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 288s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 288s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 288s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-OK9K22/virtual_image.socket 288s # libfprint-context-DEBUG: created 288s # libfprint-device-DEBUG: Device reported probe completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:47.399: 65317943: ../libfprint/drivers/virtual-image.c:216 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:47.399: 65317986: ../libfprint/drivers/virtual-device-listener.c:153 288s # libfprint-image_device-DEBUG: Image device open completed 288s # libfprint-device-DEBUG: Device reported open completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:47.500: 65418848: ../libfprint/drivers/virtual-image.c:244 288s # libfprint-image_device-DEBUG: Image device close completed 288s # libfprint-device-DEBUG: Device reported close completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 288s ok 6 /device/sync/get_device_id 288s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 288s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 288s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 288s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 288s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 288s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 288s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-CS9Z12/virtual_image.socket 288s # libfprint-context-DEBUG: created 288s # libfprint-device-DEBUG: Device reported probe completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:47.607: 65525224: ../libfprint/drivers/virtual-image.c:216 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:47.607: 65525281: ../libfprint/drivers/virtual-device-listener.c:153 288s # libfprint-image_device-DEBUG: Image device open completed 288s # libfprint-device-DEBUG: Device reported open completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:47.707: 65626060: ../libfprint/drivers/virtual-image.c:244 288s # libfprint-image_device-DEBUG: Image device close completed 288s # libfprint-device-DEBUG: Device reported close completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 288s ok 7 /device/sync/get_name 288s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 288s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 288s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 288s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 288s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 288s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 288s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-26P612/virtual_image.socket 288s # libfprint-context-DEBUG: created 288s # libfprint-device-DEBUG: Device reported probe completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:47.814: 65732245: ../libfprint/drivers/virtual-image.c:216 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:47.814: 65732298: ../libfprint/drivers/virtual-device-listener.c:153 288s # libfprint-image_device-DEBUG: Image device open completed 288s # libfprint-device-DEBUG: Device reported open completion 288s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 288s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 288s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:47.915: 65833198: ../libfprint/drivers/virtual-image.c:244 289s # libfprint-image_device-DEBUG: Image device close completed 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 289s ok 8 /device/sync/get_scan_type 289s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 289s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 289s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 289s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 289s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 289s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 289s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-E1GC22/virtual_image.socket 289s # libfprint-context-DEBUG: created 289s # libfprint-device-DEBUG: Device reported probe completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:48.021: 65939166: ../libfprint/drivers/virtual-image.c:216 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:48.021: 65939212: ../libfprint/drivers/virtual-device-listener.c:153 289s # libfprint-image_device-DEBUG: Image device open completed 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:48.121: 66040140: ../libfprint/drivers/virtual-image.c:244 289s # libfprint-image_device-DEBUG: Image device close completed 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 289s ok 9 /device/sync/get_finger_status 289s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 289s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 289s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 289s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 289s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 289s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 289s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-W9ZD22/virtual_image.socket 289s # libfprint-context-DEBUG: created 289s # libfprint-device-DEBUG: Device reported probe completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:48.227: 66145948: ../libfprint/drivers/virtual-image.c:216 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:48.227: 66146038: ../libfprint/drivers/virtual-device-listener.c:153 289s # libfprint-image_device-DEBUG: Image device open completed 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:48.328: 66246986: ../libfprint/drivers/virtual-image.c:244 289s # libfprint-image_device-DEBUG: Image device close completed 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 289s ok 10 /device/sync/get_nr_enroll_stages 289s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 289s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 289s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 289s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 289s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 289s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 289s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-0EVL22/virtual_image.socket 289s # libfprint-context-DEBUG: created 289s # libfprint-device-DEBUG: Device reported probe completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:48.434: 66353135: ../libfprint/drivers/virtual-image.c:216 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:48.435: 66353181: ../libfprint/drivers/virtual-device-listener.c:153 289s # libfprint-image_device-DEBUG: Image device open completed 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:48.535: 66454115: ../libfprint/drivers/virtual-image.c:244 289s # libfprint-image_device-DEBUG: Image device close completed 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 289s ok 11 /device/sync/supports_identify 289s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 289s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 289s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 289s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 289s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 289s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 289s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-J4W012/virtual_image.socket 289s # libfprint-context-DEBUG: created 289s # libfprint-device-DEBUG: Device reported probe completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:48.642: 66560566: ../libfprint/drivers/virtual-image.c:216 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:48.642: 66560691: ../libfprint/drivers/virtual-device-listener.c:153 289s # libfprint-image_device-DEBUG: Image device open completed 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:48.743: 66661326: ../libfprint/drivers/virtual-image.c:244 289s # libfprint-image_device-DEBUG: Image device close completed 289s # libfprint-device-DEBUG: Device reported close completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 289s ok 12 /device/sync/supports_capture 289s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 289s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 289s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 289s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 289s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 289s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 289s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-HDR712/virtual_image.socket 289s # libfprint-context-DEBUG: created 289s # libfprint-device-DEBUG: Device reported probe completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:48.849: 66767819: ../libfprint/drivers/virtual-image.c:216 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:48.849: 66767867: ../libfprint/drivers/virtual-device-listener.c:153 289s # libfprint-image_device-DEBUG: Image device open completed 289s # libfprint-device-DEBUG: Device reported open completion 289s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 289s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 289s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:48.950: 66868964: ../libfprint/drivers/virtual-image.c:244 290s # libfprint-image_device-DEBUG: Image device close completed 290s # libfprint-device-DEBUG: Device reported close completion 290s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 290s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 290s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 290s ok 13 /device/sync/has_storage 290s # Start of open tests 290s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 290s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 290s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 290s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 290s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 290s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 290s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-DN5C22/virtual_image.socket 290s # libfprint-context-DEBUG: created 290s # libfprint-device-DEBUG: Device reported probe completion 290s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 290s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 290s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:49.057: 66975197: ../libfprint/drivers/virtual-image.c:216 290s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:49.057: 66975256: ../libfprint/drivers/virtual-device-listener.c:153 290s Executing: libfprint-2/fp-device.test 290s # libfprint-image_device-DEBUG: Image device open completed 290s # libfprint-device-DEBUG: Device reported open completion 290s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 290s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 290s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:49.157: 67076096: ../libfprint/drivers/virtual-image.c:244 290s # libfprint-image_device-DEBUG: Image device close completed 290s # libfprint-device-DEBUG: Device reported close completion 290s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 290s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 290s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 290s ok 14 /device/sync/open/notify 290s # End of open tests 290s # Start of close tests 290s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 290s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 290s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 290s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 290s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 290s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 290s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-LTOE22/virtual_image.socket 290s # libfprint-context-DEBUG: created 290s # libfprint-device-DEBUG: Device reported probe completion 290s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 290s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 290s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:49.263: 67182154: ../libfprint/drivers/virtual-image.c:216 290s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:49.264: 67182208: ../libfprint/drivers/virtual-device-listener.c:153 290s # libfprint-image_device-DEBUG: Image device open completed 290s # libfprint-device-DEBUG: Device reported open completion 290s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 290s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 290s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:49.364: 67283091: ../libfprint/drivers/virtual-image.c:244 290s # libfprint-image_device-DEBUG: Image device close completed 290s # libfprint-device-DEBUG: Device reported close completion 290s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 290s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 290s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 290s ok 15 /device/sync/close/notify 290s # End of close tests 290s # Start of identify tests 290s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 290s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 290s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 290s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 290s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 290s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 290s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-0TQJ22/virtual_image.socket 290s # libfprint-context-DEBUG: created 290s # libfprint-device-DEBUG: Device reported probe completion 290s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 290s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 290s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:49.470: 67388790: ../libfprint/drivers/virtual-image.c:216 290s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:49.470: 67388841: ../libfprint/drivers/virtual-device-listener.c:153 290s # libfprint-image_device-DEBUG: Image device open completed 290s # libfprint-device-DEBUG: Device reported open completion 290s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 290s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 290s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:49.571: 67489654: ../libfprint/drivers/virtual-image.c:244 290s # libfprint-image_device-DEBUG: Image device close completed 290s # libfprint-device-DEBUG: Device reported close completion 290s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 290s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 290s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 290s ok 16 /device/sync/identify/cancelled 290s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 290s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 290s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 290s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 290s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 290s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 290s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-YM2312/virtual_image.socket 290s # libfprint-context-DEBUG: created 290s # libfprint-device-DEBUG: Device reported probe completion 290s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 290s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 290s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:49.678: 67596195: ../libfprint/drivers/virtual-image.c:216 290s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_device_connection-DEBUG: 05:01:49.678: 67596258: ../libfprint/drivers/virtual-device-listener.c:153 290s # libfprint-image_device-DEBUG: Image device open completed 290s # libfprint-device-DEBUG: Device reported open completion 290s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 290s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 290s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2338): libfprint-virtual_image-DEBUG: 05:01:49.779: 67697293: ../libfprint/drivers/virtual-image.c:244 290s # libfprint-image_device-DEBUG: Image device close completed 290s # libfprint-device-DEBUG: Device reported close completion 290s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 290s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 290s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 290s ok 17 /device/sync/identify/null-prints 290s # End of identify tests 290s # End of sync tests 290s # End of device tests 290s PASS: libfprint-2/fp-device.test 290s Running test: libfprint-2/fpi-assembling.test 290s TAP version 14 290s # random seed: R02S52b1c2e3f913c6b76cf3efb4a26b09d5 290s 1..1 290s # Start of assembling tests 291s # libfprint-assembling-DEBUG: calc delta completed in 0.102630 secs 291s # libfprint-assembling-DEBUG: calc delta completed in 0.102475 secs 291s # libfprint-assembling-DEBUG: errors: 0 rev: 130848 291s # libfprint-assembling-DEBUG: calc delta completed in 0.101896 secs 291s # libfprint-assembling-DEBUG: height is 310 291s ok 1 /assembling/frames 291s # End of assembling tests 291s PASS: libfprint-2/fpi-assembling.test 291s Running test: libfprint-2/driver-vfs5011.test 291s ** (umockdev-run:2380): DEBUG: 05:01:50.276: umockdev.vala:127: Created udev test bed /tmp/umockdev.7RJI22 291s ** (umockdev-run:2380): DEBUG: 05:01:50.277: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2/2-6 291s ** (umockdev-run:2380): DEBUG: 05:01:50.278: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb2/2-6 (subsystem usb) 291s ** (umockdev-run:2380): DEBUG: 05:01:50.282: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.7RJI22/dev/bus/usb/002/017 291s ** (umockdev-run:2380): DEBUG: 05:01:50.282: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb2 291s ** (umockdev-run:2380): DEBUG: 05:01:50.283: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb2 (subsystem usb) 291s ** (umockdev-run:2380): DEBUG: 05:01:50.285: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.7RJI22/dev/bus/usb/002/001 291s ** (umockdev-run:2380): DEBUG: 05:01:50.286: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 291s ** (umockdev-run:2380): DEBUG: 05:01:50.286: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 291s (umockdev-run:2380): GLib-GIO-DEBUG: 05:01:50.289: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 292s (process:2384): libfprint-context-DEBUG: 05:01:50.414: Initializing FpContext (libfprint version 1.94.9+tod1) 292s (process:2384): libfprint-tod-DEBUG: 05:01:50.415: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 292s (process:2384): libfprint-context-DEBUG: 05:01:50.417: No driver found for USB device 1D6B:0002 292s (process:2384): libfprint-device-DEBUG: 05:01:50.418: Device reported probe completion 292s (process:2384): libfprint-device-DEBUG: 05:01:50.418: Completing action FPI_DEVICE_ACTION_PROBE in idle! 292s (process:2384): libfprint-device-DEBUG: 05:01:50.418: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.420: [vfs5011] DEV_OPEN_NUM_STATES entering state 0 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.420: [vfs5011] DEVICE OPEN entering state 0 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.420: Sending vfs5011_cmd_01 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.421: [vfs5011] DEVICE OPEN entering state 1 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.422: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.422: Got 38 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.423: [vfs5011] DEVICE OPEN entering state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.423: Sending vfs5011_cmd_19 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.423: [vfs5011] DEVICE OPEN entering state 3 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.424: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.424: Got 64 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.425: [vfs5011] DEVICE OPEN entering state 4 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.425: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.425: Got 4 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.425: [vfs5011] DEVICE OPEN entering state 5 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.425: Sending vfs5011_init_00 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.426: [vfs5011] DEVICE OPEN entering state 6 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.426: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.427: Got 6 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.427: [vfs5011] DEVICE OPEN entering state 7 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.427: Sending vfs5011_init_01 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.428: [vfs5011] DEVICE OPEN entering state 8 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.428: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.429: Got 7 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.429: [vfs5011] DEVICE OPEN entering state 9 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.429: Sending vfs5011_init_02 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.430: [vfs5011] DEVICE OPEN entering state 10 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.430: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.431: [vfs5011] DEVICE OPEN entering state 11 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.431: Sending vfs5011_cmd_01 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.431: [vfs5011] DEVICE OPEN entering state 12 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.431: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.432: Got 38 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.432: [vfs5011] DEVICE OPEN entering state 13 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.432: Sending vfs5011_cmd_1A 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.433: [vfs5011] DEVICE OPEN entering state 14 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.433: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.434: [vfs5011] DEVICE OPEN entering state 15 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.434: Sending vfs5011_init_03 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.434: [vfs5011] DEVICE OPEN entering state 16 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.434: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.435: [vfs5011] DEVICE OPEN entering state 17 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.435: Sending vfs5011_init_04 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.436: [vfs5011] DEVICE OPEN entering state 18 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.436: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.437: [vfs5011] DEVICE OPEN entering state 19 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.437: Receiving 256 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.437: Got 256 bytes out of 256 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.437: [vfs5011] DEVICE OPEN entering state 20 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.437: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.438: Got 32 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.438: [vfs5011] DEVICE OPEN entering state 21 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.438: Sending vfs5011_cmd_1A 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.439: [vfs5011] DEVICE OPEN entering state 22 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.439: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.440: [vfs5011] DEVICE OPEN entering state 23 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.440: Sending vfs5011_init_05 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.441: [vfs5011] DEVICE OPEN entering state 24 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.441: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.442: [vfs5011] DEVICE OPEN entering state 25 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.442: Sending vfs5011_cmd_01 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.442: [vfs5011] DEVICE OPEN entering state 26 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.442: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.443: Got 38 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.443: [vfs5011] DEVICE OPEN entering state 27 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.443: Sending vfs5011_init_06 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.444: [vfs5011] DEVICE OPEN entering state 28 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.444: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.445: [vfs5011] DEVICE OPEN entering state 29 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.445: Receiving 17216 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.446: Got 17216 bytes out of 17216 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.446: [vfs5011] DEVICE OPEN entering state 30 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.446: Receiving 32 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.447: Got 32 bytes out of 32 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.447: [vfs5011] DEVICE OPEN entering state 31 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.447: Sending vfs5011_init_07 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.447: [vfs5011] DEVICE OPEN entering state 32 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.447: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.448: [vfs5011] DEVICE OPEN entering state 33 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.448: Receiving 45056 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.449: Got 45056 bytes out of 45056 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.449: [vfs5011] DEVICE OPEN entering state 34 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.449: Sending vfs5011_init_08 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.450: [vfs5011] DEVICE OPEN entering state 35 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.450: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.451: [vfs5011] DEVICE OPEN entering state 36 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.451: Receiving 16896 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.451: Got 16896 bytes out of 16896 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.451: [vfs5011] DEVICE OPEN entering state 37 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.451: Sending vfs5011_init_09 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.452: [vfs5011] DEVICE OPEN entering state 38 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.452: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.453: [vfs5011] DEVICE OPEN entering state 39 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.453: Receiving 4928 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.453: Got 4928 bytes out of 4928 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.453: [vfs5011] DEVICE OPEN entering state 40 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.453: Sending vfs5011_init_10 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.454: [vfs5011] DEVICE OPEN entering state 41 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.454: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.454: [vfs5011] DEVICE OPEN entering state 42 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.454: Receiving 5632 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.455: Got 5632 bytes out of 5632 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.455: [vfs5011] DEVICE OPEN entering state 43 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.455: Sending vfs5011_init_11 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.455: [vfs5011] DEVICE OPEN entering state 44 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.455: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.456: [vfs5011] DEVICE OPEN entering state 45 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.456: Receiving 5632 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.457: Got 5632 bytes out of 5632 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.457: [vfs5011] DEVICE OPEN entering state 46 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.457: Sending vfs5011_init_12 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.457: [vfs5011] DEVICE OPEN entering state 47 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.457: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.458: [vfs5011] DEVICE OPEN entering state 48 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.458: Receiving 3328 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.458: Got 3328 bytes out of 3328 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.458: [vfs5011] DEVICE OPEN entering state 49 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.458: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.459: Got 32 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.459: [vfs5011] DEVICE OPEN entering state 50 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.459: Sending vfs5011_init_13 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.459: [vfs5011] DEVICE OPEN entering state 51 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.460: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.460: [vfs5011] DEVICE OPEN entering state 52 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.460: Sending vfs5011_cmd_1A 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.461: [vfs5011] DEVICE OPEN entering state 53 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.461: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.461: [vfs5011] DEVICE OPEN entering state 54 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.461: Sending vfs5011_init_03 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.462: [vfs5011] DEVICE OPEN entering state 55 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.462: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.462: [vfs5011] DEVICE OPEN entering state 56 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.462: Sending vfs5011_init_14 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.463: [vfs5011] DEVICE OPEN entering state 57 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.463: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.463: [vfs5011] DEVICE OPEN entering state 58 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.463: Receiving 4800 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.464: Got 4800 bytes out of 4800 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.464: [vfs5011] DEVICE OPEN entering state 59 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.464: Sending vfs5011_cmd_1A 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.464: [vfs5011] DEVICE OPEN entering state 60 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.464: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.465: [vfs5011] DEVICE OPEN entering state 61 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.465: Sending vfs5011_init_02 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.465: [vfs5011] DEVICE OPEN entering state 62 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.465: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.466: [vfs5011] DEVICE OPEN entering state 63 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.466: Sending vfs5011_cmd_27 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.466: [vfs5011] DEVICE OPEN entering state 64 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.466: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.467: Got 22 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.467: [vfs5011] DEVICE OPEN entering state 65 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.467: Sending vfs5011_cmd_1A 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.468: [vfs5011] DEVICE OPEN entering state 66 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.468: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.468: [vfs5011] DEVICE OPEN entering state 67 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.468: Sending vfs5011_init_15 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.469: [vfs5011] DEVICE OPEN entering state 68 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.469: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.469: [vfs5011] DEVICE OPEN entering state 69 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.469: Sending vfs5011_init_16 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.470: [vfs5011] DEVICE OPEN entering state 70 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.470: Receiving 2368 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.470: Got 2368 bytes out of 2368 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.470: [vfs5011] DEVICE OPEN entering state 71 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.470: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.471: Got 36 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.471: [vfs5011] DEVICE OPEN entering state 72 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.471: Receiving 4800 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.471: Got 4800 bytes out of 4800 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.471: [vfs5011] DEVICE OPEN entering state 73 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.471: Sending vfs5011_init_17 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.472: [vfs5011] DEVICE OPEN entering state 74 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.472: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.472: [vfs5011] DEVICE OPEN entering state 75 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.472: Sending vfs5011_init_18 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.473: [vfs5011] DEVICE OPEN entering state 76 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.473: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.473: [vfs5011] DEVICE OPEN completed successfully 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.473: [vfs5011] DEV_OPEN_NUM_STATES completed successfully 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.473: Image device open completed 292s (process:2384): libfprint-device-DEBUG: 05:01:50.473: Device reported open completion 292s (process:2384): libfprint-device-DEBUG: 05:01:50.473: Completing action FPI_DEVICE_ACTION_OPEN in idle! 292s (process:2384): libfprint-device-DEBUG: 05:01:50.473: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 292s (process:2384): libfprint-device-DEBUG: 05:01:50.473: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.474: Activating image device 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.474: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.474: device initialized 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.474: creating ssm 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.474: starting ssm 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.474: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 0 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.474: main_loop: state 0 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.474: [vfs5011] ACTIVATE REQUEST entering state 0 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.474: Sending vfs5011_cmd_04 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.474: ssm done, getting out 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.474: [vfs5011] ACTIVATE REQUEST entering state 1 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.474: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.475: Got 64 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.475: [vfs5011] ACTIVATE REQUEST entering state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.475: Receiving 84032 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.476: Got 176 bytes out of 84032 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.476: [vfs5011] ACTIVATE REQUEST entering state 3 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.476: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.477: [vfs5011] ACTIVATE REQUEST entering state 4 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.477: Sending vfs5011_cmd_1A 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.477: [vfs5011] ACTIVATE REQUEST entering state 5 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.477: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.478: [vfs5011] ACTIVATE REQUEST entering state 6 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.478: Sending vfs5011_prepare_00 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.478: [vfs5011] ACTIVATE REQUEST entering state 7 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.478: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.479: [vfs5011] ACTIVATE REQUEST entering state 8 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.479: Sending vfs5011_cmd_1A 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.479: [vfs5011] ACTIVATE REQUEST entering state 9 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.479: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.480: [vfs5011] ACTIVATE REQUEST entering state 10 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.480: Sending vfs5011_prepare_01 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.480: [vfs5011] ACTIVATE REQUEST entering state 11 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.480: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.481: [vfs5011] ACTIVATE REQUEST entering state 12 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.481: Sending vfs5011_prepare_02 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.481: [vfs5011] ACTIVATE REQUEST entering state 13 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.481: Receiving 2368 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.482: Got 2368 bytes out of 2368 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.482: [vfs5011] ACTIVATE REQUEST entering state 14 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.482: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.482: Got 36 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.482: [vfs5011] ACTIVATE REQUEST entering state 15 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.482: Receiving 4800 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.483: Got 4800 bytes out of 4800 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.483: [vfs5011] ACTIVATE REQUEST entering state 16 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.483: Sending vfs5011_prepare_03 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.483: [vfs5011] ACTIVATE REQUEST entering state 17 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.483: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.484: [vfs5011] ACTIVATE REQUEST entering state 18 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.484: Sending vfs5011_prepare_04 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.484: [vfs5011] ACTIVATE REQUEST entering state 19 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.484: Receiving 2368 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.485: [vfs5011] ACTIVATE REQUEST completed successfully 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.485: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 1 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.485: main_loop: state 1 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.485: capture_init 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.485: Image device activation completed 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.485: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.485: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 292s (process:2384): libfprint-device-DEBUG: 05:01:50.485: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.485: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.485: main_loop: state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.485: capture_chunk_async: capture 256 lines, already have 0 292s (process:2384): libfprint-device-DEBUG: 05:01:50.486: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.486: Image device reported finger status: on 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.486: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.486: process_chunk: got 61440 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.486: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.486: main_loop: state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.486: capture_chunk_async: capture 256 lines, already have 6 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.487: Image device reported finger status: on 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.487: process_chunk: got 61440 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.487: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.487: main_loop: state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.487: capture_chunk_async: capture 256 lines, already have 25 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.488: Image device reported finger status: on 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.488: process_chunk: got 61440 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.488: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.488: main_loop: state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.488: capture_chunk_async: capture 256 lines, already have 54 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.488: Image device reported finger status: on 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.489: process_chunk: got 61440 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.489: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.489: main_loop: state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.489: capture_chunk_async: capture 256 lines, already have 89 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.489: Image device reported finger status: on 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.489: process_chunk: got 61440 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.490: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.490: main_loop: state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.490: capture_chunk_async: capture 256 lines, already have 117 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.490: Image device reported finger status: on 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.490: process_chunk: got 61440 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.490: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.490: main_loop: state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.490: capture_chunk_async: capture 256 lines, already have 144 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.491: Image device reported finger status: on 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.491: process_chunk: got 61440 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.491: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.491: main_loop: state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.491: capture_chunk_async: capture 256 lines, already have 180 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.492: Image device reported finger status: on 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.492: process_chunk: got 61440 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.492: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.492: main_loop: state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.492: capture_chunk_async: capture 256 lines, already have 273 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.493: Image device reported finger status: on 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.493: process_chunk: got 61440 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.493: process_chunk: got 50 empty lines, finishing 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.493: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 3 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.493: main_loop: state 3 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.494: [vfs5011] DEV_ACTIVATE_NUM_STATES entering state 4 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.494: main_loop: state 4 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.494: [vfs5011] PREPARE CAPTURE entering state 0 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.494: Sending vfs5011_cmd_04 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.494: [vfs5011] PREPARE CAPTURE entering state 1 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.494: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.495: Got 64 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.495: [vfs5011] PREPARE CAPTURE entering state 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.495: Receiving 84032 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.496: Got 176 bytes out of 84032 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.496: [vfs5011] PREPARE CAPTURE entering state 3 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.496: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.496: [vfs5011] PREPARE CAPTURE entering state 4 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.496: Sending vfs5011_cmd_1A 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.497: [vfs5011] PREPARE CAPTURE entering state 5 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.497: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.497: [vfs5011] PREPARE CAPTURE entering state 6 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.497: Sending vfs5011_prepare_00 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.498: [vfs5011] PREPARE CAPTURE entering state 7 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.498: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.499: [vfs5011] PREPARE CAPTURE entering state 8 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.499: Sending vfs5011_cmd_1A 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.500: [vfs5011] PREPARE CAPTURE entering state 9 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.500: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.500: [vfs5011] PREPARE CAPTURE entering state 10 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.501: Sending vfs5011_prepare_01 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.501: [vfs5011] PREPARE CAPTURE entering state 11 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.501: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.502: [vfs5011] PREPARE CAPTURE entering state 12 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.502: Sending vfs5011_prepare_02 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.503: [vfs5011] PREPARE CAPTURE entering state 13 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.503: Receiving 2368 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.504: Got 2368 bytes out of 2368 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.504: [vfs5011] PREPARE CAPTURE entering state 14 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.504: Receiving 64 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.504: Got 36 bytes out of 64 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.504: [vfs5011] PREPARE CAPTURE entering state 15 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.504: Receiving 4800 bytes 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.505: Got 4800 bytes out of 4800 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.505: [vfs5011] PREPARE CAPTURE entering state 16 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.505: Sending vfs5011_prepare_03 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.506: [vfs5011] PREPARE CAPTURE entering state 17 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.506: Receiving 64 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.507: [vfs5011] PREPARE CAPTURE entering state 18 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.507: Sending vfs5011_prepare_04 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.508: [vfs5011] PREPARE CAPTURE entering state 19 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.508: Receiving 2368 bytes 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.508: [vfs5011] PREPARE CAPTURE completed successfully 292s (process:2384): libfprint-SSM-DEBUG: 05:01:50.508: [vfs5011] DEV_ACTIVATE_NUM_STATES completed successfully 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.508: finishing 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 1740200510509004 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 1 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 5 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 4 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 4 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 3 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 3 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 5 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 4 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 27 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 27 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 27 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 27 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 5 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 30 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 30 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 5 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 5 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 30 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 30 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 30 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 30 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 30 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 4 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 4 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 30 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 30 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 30 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 30 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 30 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 30 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 11 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 30 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 27 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 26 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 5 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 4 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.509: 2 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: offsets_filtered: 1740200510510027 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 5 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 5 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 5 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 5 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 5 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 27 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 27 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 27 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 27 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 27 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 27 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 27 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 29 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 28 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 6 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 9 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 8 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 7 292s (process:2384): libfprint-assembling-DEBUG: 05:01:50.510: 2 292s (process:2384): libfprint-vfs5011-DEBUG: 05:01:50.510: Image captured, committing 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.510: Image device captured an image 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.511: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 292s (process:2384): libfprint-device-DEBUG: 05:01:50.511: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2384): libfprint-device-DEBUG: 05:01:50.511: Device reported finger status change: FP_FINGER_STATUS_NONE 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.511: Image device reported finger status: off 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.511: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.511: Deactivating image device 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.511: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.511: Image device deactivation completed 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.511: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 292s (process:2384): libfprint-image-DEBUG: 05:01:50.526: Minutiae scan completed in 0.014157 secs 292s (process:2384): libfprint-device-DEBUG: 05:01:50.526: Device reported capture completion 292s (process:2384): libfprint-device-DEBUG: 05:01:50.527: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 292s (process:2384): libfprint-device-DEBUG: 05:01:50.527: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 292s (process:2384): libfprint-image_device-DEBUG: 05:01:50.528: Image device close completed 292s (process:2384): libfprint-device-DEBUG: 05:01:50.528: Device reported close completion 292s (process:2384): libfprint-device-DEBUG: 05:01:50.529: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 292s (process:2384): libfprint-device-DEBUG: 05:01:50.529: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 292s ** (umockdev-run:2380): DEBUG: 05:01:50.707: umockdev.vala:154: Removing test bed /tmp/umockdev.7RJI22 292s (umockdev-run:2380): GLib-DEBUG: 05:01:50.711: unsetenv() is not thread-safe and should not be used after threads are created 292s Comparing PNGs /tmp/libfprint-umockdev-test-_bywbs_j/capture.png and /usr/share/installed-tests/libfprint-2/vfs5011/capture.png 292s PASS: libfprint-2/driver-vfs5011.test 292s Running test: libfprint-2/driver-aes3500.test 292s ** (umockdev-run:2393): DEBUG: 05:01:50.804: umockdev.vala:127: Created udev test bed /tmp/umockdev.DXU612 292s ** (umockdev-run:2393): DEBUG: 05:01:50.805: 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 292s ** (umockdev-run:2393): DEBUG: 05:01:50.807: 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) 292s ** (umockdev-run:2393): DEBUG: 05:01:50.810: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DXU612/dev/bus/usb/003/004 292s ** (umockdev-run:2393): DEBUG: 05:01:50.811: 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 292s ** (umockdev-run:2393): DEBUG: 05:01:50.813: 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) 292s ** (umockdev-run:2393): DEBUG: 05:01:50.816: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DXU612/dev/bus/usb/003/003 292s ** (umockdev-run:2393): DEBUG: 05:01:50.816: 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 292s ** (umockdev-run:2393): DEBUG: 05:01:50.818: 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) 292s ** (umockdev-run:2393): DEBUG: 05:01:50.821: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DXU612/dev/bus/usb/003/002 292s ** (umockdev-run:2393): DEBUG: 05:01:50.821: 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 292s ** (umockdev-run:2393): DEBUG: 05:01:50.823: 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) 292s ** (umockdev-run:2393): DEBUG: 05:01:50.827: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DXU612/dev/bus/usb/003/001 292s ** (umockdev-run:2393): DEBUG: 05:01:50.827: 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 292s ** (umockdev-run:2393): DEBUG: 05:01:50.828: 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) 292s ** (umockdev-run:2393): DEBUG: 05:01:50.831: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 292s ** (umockdev-run:2393): DEBUG: 05:01:50.832: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 (subsystem pci) 292s ** (umockdev-run:2393): DEBUG: 05:01:50.834: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 292s ** (umockdev-run:2393): DEBUG: 05:01:50.835: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 (subsystem pci) 292s ** (umockdev-run:2393): DEBUG: 05:01:50.837: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0 292s ** (umockdev-run:2393): DEBUG: 05:01:50.838: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0 (subsystem pci) 292s (umockdev-run:2393): GLib-GIO-DEBUG: 05:01:50.840: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 292s (process:2397): libfprint-context-DEBUG: 05:01:50.948: Initializing FpContext (libfprint version 1.94.9+tod1) 292s (process:2397): libfprint-tod-DEBUG: 05:01:50.948: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 292s (process:2397): libfprint-context-DEBUG: 05:01:50.952: No driver found for USB device 2230:0006 292s (process:2397): libfprint-context-DEBUG: 05:01:50.952: No driver found for USB device 2230:0006 292s (process:2397): libfprint-context-DEBUG: 05:01:50.952: No driver found for USB device 1D6B:0002 292s (process:2397): libfprint-device-DEBUG: 05:01:50.953: Device reported probe completion 292s (process:2397): libfprint-device-DEBUG: 05:01:50.953: Completing action FPI_DEVICE_ACTION_PROBE in idle! 292s (process:2397): libfprint-device-DEBUG: 05:01:50.953: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.956: Image device open completed 292s (process:2397): libfprint-device-DEBUG: 05:01:50.956: Device reported open completion 292s (process:2397): libfprint-device-DEBUG: 05:01:50.956: Completing action FPI_DEVICE_ACTION_OPEN in idle! 292s (process:2397): libfprint-device-DEBUG: 05:01:50.956: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 292s (process:2397): libfprint-device-DEBUG: 05:01:50.956: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.956: Activating image device 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.956: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 292s (process:2397): libfprint-aeslib-DEBUG: 05:01:50.956: write 50 regs 292s (process:2397): libfprint-aeslib-DEBUG: 05:01:50.965: all registers written 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.966: Image device activation completed 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.966: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.966: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 292s (process:2397): libfprint-aeslib-DEBUG: 05:01:50.966: write 6 regs 292s (process:2397): libfprint-device-DEBUG: 05:01:50.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2397): libfprint-aeslib-DEBUG: 05:01:50.969: all registers written 292s (process:2397): libfprint-device-DEBUG: 05:01:50.970: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.970: Image device reported finger status: on 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.970: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 292s (process:2397): libfprint-aes3k-DEBUG: 05:01:50.970: frame header byte e0 292s (process:2397): libfprint-aes3k-DEBUG: 05:01:50.971: frame header byte e1 292s (process:2397): libfprint-aes3k-DEBUG: 05:01:50.971: frame header byte e2 292s (process:2397): libfprint-aes3k-DEBUG: 05:01:50.971: frame header byte e3 292s (process:2397): libfprint-aes3k-DEBUG: 05:01:50.971: frame header byte e4 292s (process:2397): libfprint-aes3k-DEBUG: 05:01:50.971: frame header byte e5 292s (process:2397): libfprint-aes3k-DEBUG: 05:01:50.971: frame header byte e6 292s (process:2397): libfprint-aes3k-DEBUG: 05:01:50.971: frame header byte e7 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.971: Image device captured an image 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.972: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 292s (process:2397): libfprint-device-DEBUG: 05:01:50.972: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2397): libfprint-device-DEBUG: 05:01:50.972: Device reported finger status change: FP_FINGER_STATUS_NONE 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.972: Image device reported finger status: off 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.972: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.972: Deactivating image device 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.972: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.972: Image device deactivation completed 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.972: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 292s (process:2397): libfprint-image-DEBUG: 05:01:50.992: Minutiae scan completed in 0.019565 secs 292s (process:2397): libfprint-device-DEBUG: 05:01:50.992: Device reported capture completion 292s (process:2397): libfprint-device-DEBUG: 05:01:50.992: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 292s (process:2397): libfprint-device-DEBUG: 05:01:50.992: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 292s (process:2397): libfprint-image_device-DEBUG: 05:01:50.993: Image device close completed 292s (process:2397): libfprint-device-DEBUG: 05:01:50.993: Device reported close completion 292s (process:2397): libfprint-device-DEBUG: 05:01:50.993: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 292s (process:2397): libfprint-device-DEBUG: 05:01:50.993: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 292s ** (umockdev-run:2393): DEBUG: 05:01:51.114: umockdev.vala:154: Removing test bed /tmp/umockdev.DXU612 292s (umockdev-run:2393): GLib-DEBUG: 05:01:51.124: unsetenv() is not thread-safe and should not be used after threads are created 292s Comparing PNGs /tmp/libfprint-umockdev-test-5_lpud1y/capture.png and /usr/share/installed-tests/libfprint-2/aes3500/capture.png 292s PASS: libfprint-2/driver-aes3500.test 292s Running test: libfprint-2/driver-elanmoc.test 292s ** (umockdev-run:2406): DEBUG: 05:01:51.260: umockdev.vala:127: Created udev test bed /tmp/umockdev.CTOE22 292s ** (umockdev-run:2406): DEBUG: 05:01:51.260: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 292s ** (umockdev-run:2406): DEBUG: 05:01:51.261: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 292s ** (umockdev-run:2406): DEBUG: 05:01:51.264: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.CTOE22/dev/bus/usb/001/003 292s ** (umockdev-run:2406): DEBUG: 05:01:51.264: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 292s ** (umockdev-run:2406): DEBUG: 05:01:51.265: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 292s ** (umockdev-run:2406): DEBUG: 05:01:51.267: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.CTOE22/dev/bus/usb/001/001 292s ** (umockdev-run:2406): DEBUG: 05:01:51.268: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 292s ** (umockdev-run:2406): DEBUG: 05:01:51.268: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 292s (process:2410): libfprint-context-DEBUG: 05:01:51.369: Initializing FpContext (libfprint version 1.94.9+tod1) 292s (process:2410): libfprint-tod-DEBUG: 05:01:51.370: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.371: 69290113: ../libfprint/drivers/elanmoc/elanmoc.c:1154 292s (process:2410): libfprint-context-DEBUG: 05:01:51.372: No driver found for USB device 1D6B:0002 292s (process:2410): libfprint-device-DEBUG: 05:01:51.372: Device reported probe completion 292s (process:2410): libfprint-device-DEBUG: 05:01:51.372: Completing action FPI_DEVICE_ACTION_PROBE in idle! 292s (process:2410): libfprint-device-DEBUG: 05:01:51.372: Not updating temperature model, device can run continuously! 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.375: [elanmoc] DEV_INIT_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.375: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.376: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.377: [elanmoc] DEV_INIT_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.377: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.377: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.378: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.379: [elanmoc] DEV_INIT_STATES entering state 2 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.379: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.379: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.380: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.381: elanmoc FW Version 8004 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.381: [elanmoc] DEV_INIT_STATES entering state 3 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.381: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.381: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.381: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.382: elanmoc last_read DIM 0x57(87) 0x6B(107) 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.382: [elanmoc] DEV_INIT_STATES entering state 4 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.382: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.383: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.383: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.384: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.384: [elanmoc] DEV_INIT_STATES completed successfully 292s (process:2410): libfprint-device-DEBUG: 05:01:51.384: Device reported open completion 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.384: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-device-DEBUG: 05:01:51.384: Completing action FPI_DEVICE_ACTION_OPEN in idle! 292s (process:2410): libfprint-device-DEBUG: 05:01:51.384: Not updating temperature model, device can run continuously! 292s (process:2410): libfprint-device-DEBUG: 05:01:51.385: Not updating temperature model, device can run continuously! 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.385: [elanmoc] MOC_ENROLL_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.385: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.386: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.387: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.387: [elanmoc] MOC_ENROLL_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.387: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.387: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.388: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.389: ##### Re-Enrollment Case! ##### 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.389: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.389: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.389: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.389: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-device-DEBUG: 05:01:51.390: Device reported enroll progress, reported 1 of 9 have been completed 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.390: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.391: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.391: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.391: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-device-DEBUG: 05:01:51.392: Device reported enroll progress, reported 2 of 9 have been completed 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.392: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.392: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.393: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.393: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-device-DEBUG: 05:01:51.394: Device reported enroll progress, reported 3 of 9 have been completed 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.394: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.394: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.395: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.395: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-device-DEBUG: 05:01:51.396: Device reported enroll progress, reported 4 of 9 have been completed 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.396: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.396: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.397: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.397: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-device-DEBUG: 05:01:51.398: Device reported enroll progress, reported 5 of 9 have been completed 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.398: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.398: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.399: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.399: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-device-DEBUG: 05:01:51.400: Device reported enroll progress, reported 6 of 9 have been completed 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.400: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.400: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.401: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.401: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-device-DEBUG: 05:01:51.402: Device reported enroll progress, reported 7 of 9 have been completed 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.402: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.402: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.403: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.403: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-device-DEBUG: 05:01:51.404: Device reported enroll progress, reported 7 of 9 have been completed 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.404: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.404: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.405: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.405: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-device-DEBUG: 05:01:51.406: Device reported enroll progress, reported 8 of 9 have been completed 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.406: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.406: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.406: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.407: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-device-DEBUG: 05:01:51.407: Device reported enroll progress, reported 8 of 9 have been completed 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.408: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.408: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.408: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.409: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-device-DEBUG: 05:01:51.409: Device reported enroll progress, reported 9 of 9 have been completed 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.409: [elanmoc] MOC_ENROLL_NUM_STATES entering state 3 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.409: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.410: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.410: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.411: elanmoc_commit_cb success 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.411: Enrollment was successful! 292s (process:2410): libfprint-device-DEBUG: 05:01:51.411: Device reported enroll completion 292s (process:2410): libfprint-device-DEBUG: 05:01:51.411: Print for finger FP_FINGER_UNKNOWN enrolled 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.411: [elanmoc] MOC_ENROLL_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.411: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-device-DEBUG: 05:01:51.411: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 292s (process:2410): libfprint-device-DEBUG: 05:01:51.411: Not updating temperature model, device can run continuously! 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.412: [elanmoc] MOC_LIST_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.412: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.412: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.413: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01) 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.413: [elanmoc] MOC_LIST_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.413: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.414: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.414: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.415: [elanmoc] MOC_LIST_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.415: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.415: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.416: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.417: [elanmoc] MOC_LIST_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.417: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.417: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.418: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.419: [elanmoc] MOC_LIST_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.419: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.419: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.420: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.420: [elanmoc] MOC_LIST_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.420: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.421: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.421: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.422: [elanmoc] MOC_LIST_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.422: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.423: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.423: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.424: [elanmoc] MOC_LIST_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.424: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.424: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.425: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.425: [elanmoc] MOC_LIST_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.425: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.426: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.426: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.427: [elanmoc] MOC_LIST_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.427: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.428: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.428: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.429: [elanmoc] MOC_LIST_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.429: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.429: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.429: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-device-DEBUG: 05:01:51.430: Device reported listing completion 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.430: [elanmoc] MOC_LIST_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.430: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-device-DEBUG: 05:01:51.430: Completing action FPI_DEVICE_ACTION_LIST in idle! 292s (process:2410): libfprint-device-DEBUG: 05:01:51.430: Not updating temperature model, device can run continuously! 292s (process:2410): libfprint-device-DEBUG: 05:01:51.431: Not updating temperature model, device can run continuously! 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.431: [elanmoc] IDENTIFY_NUM_STATES entering state 0 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.431: elanmoc elan_identify_run_state 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.431: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.431: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.432: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.433: [elanmoc] IDENTIFY_NUM_STATES entering state 1 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.433: elanmoc elan_identify_run_state 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.433: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.433: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.433: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.434: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.435: Verify was successful! for user: 0 mesg_code: 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.435: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.435: [elanmoc] IDENTIFY_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.435: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.435: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.436: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 292s (process:2410): libfprint-device-DEBUG: 05:01:51.436: Device reported verify result 292s (process:2410): libfprint-device-DEBUG: 05:01:51.436: Device reported verify completion 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.436: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-device-DEBUG: 05:01:51.436: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 292s (process:2410): libfprint-device-DEBUG: 05:01:51.436: Not updating temperature model, device can run continuously! 292s (process:2410): libfprint-device-DEBUG: 05:01:51.437: Not updating temperature model, device can run continuously! 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.438: [elanmoc] IDENTIFY_NUM_STATES entering state 0 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.438: elanmoc elan_identify_run_state 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.438: elanmoc elan_identify_run_state IDENTIFY_SET_MODE 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.438: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.438: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.439: [elanmoc] IDENTIFY_NUM_STATES entering state 1 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.439: elanmoc elan_identify_run_state 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.439: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.439: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.440: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.440: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.441: Verify was successful! for user: 0 mesg_code: 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.441: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.442: [elanmoc] IDENTIFY_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.442: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.442: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.443: Verify/Identify successful for: FP1-00000000-0-00000000-nobody 292s (process:2410): libfprint-device-DEBUG: 05:01:51.443: Device reported identify result 292s (process:2410): libfprint-device-DEBUG: 05:01:51.443: Device reported identify completion 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.443: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-device-DEBUG: 05:01:51.443: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 292s (process:2410): libfprint-device-DEBUG: 05:01:51.443: Not updating temperature model, device can run continuously! 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.444: Delete Finger, user_id = FP1-00000000-0-00000000-nobody! 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.445: [elanmoc] DELETE_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.445: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.446: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-device-DEBUG: 05:01:51.446: Device reported deletion completion 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.446: [elanmoc] DELETE_NUM_STATES completed successfully 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.446: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-device-DEBUG: 05:01:51.446: Completing action FPI_DEVICE_ACTION_DELETE in idle! 292s (process:2410): libfprint-device-DEBUG: 05:01:51.446: Not updating temperature model, device can run continuously! 292s (process:2410): libfprint-elanmoc-DEBUG: 05:01:51.447: Elanmoc dev_exit 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.447: [elanmoc] DEV_EXIT_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.447: [elanmoc] FP_CMD_NUM_STATES entering state 0 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.448: [elanmoc] FP_CMD_NUM_STATES entering state 1 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.448: [elanmoc] DEV_EXIT_STATES completed successfully 292s (process:2410): libfprint-device-DEBUG: 05:01:51.449: Device reported close completion 292s (process:2410): libfprint-SSM-DEBUG: 05:01:51.449: [elanmoc] FP_CMD_NUM_STATES completed successfully 292s (process:2410): libfprint-device-DEBUG: 05:01:51.449: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 292s (process:2410): libfprint-device-DEBUG: 05:01:51.449: Not updating temperature model, device can run continuously! 292s enrolling 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xe6b7be239c40 (FpiDeviceElanmoc at 0x28c6b610)>, 1, None, None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xe6b7be239c40 (FpiDeviceElanmoc at 0x28c6b610)>, 2, None, None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xe6b7be239c40 (FpiDeviceElanmoc at 0x28c6b610)>, 3, None, None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xe6b7be239c40 (FpiDeviceElanmoc at 0x28c6b610)>, 4, None, None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xe6b7be239c40 (FpiDeviceElanmoc at 0x28c6b610)>, 5, None, None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xe6b7be239c40 (FpiDeviceElanmoc at 0x28c6b610)>, 6, None, None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xe6b7be239c40 (FpiDeviceElanmoc at 0x28c6b610)>, 7, None, None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xe6b7be239c40 (FpiDeviceElanmoc at 0x28c6b610)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xe6b7be239c40 (FpiDeviceElanmoc at 0x28c6b610)>, 8, None, None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xe6b7be239c40 (FpiDeviceElanmoc at 0x28c6b610)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0xe6b7be239c40 (FpiDeviceElanmoc at 0x28c6b610)>, 9, None, None, None) 292s enroll done 292s listing 292s listing done 292s verifying 292s verify done 292s async identifying 292s indentification_done: 292s deleting 292s delete done 292s ** (umockdev-run:2406): DEBUG: 05:01:51.527: umockdev.vala:154: Removing test bed /tmp/umockdev.CTOE22 292s (umockdev-run:2406): GLib-DEBUG: 05:01:51.531: unsetenv() is not thread-safe and should not be used after threads are created 292s PASS: libfprint-2/driver-elanmoc.test 292s Running test: libfprint-2/driver-egismoc-0587.test 292s ** (umockdev-run:2418): DEBUG: 05:01:51.602: umockdev.vala:127: Created udev test bed /tmp/umockdev.IYB012 292s ** (umockdev-run:2418): DEBUG: 05:01:51.602: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5 292s ** (umockdev-run:2418): DEBUG: 05:01:51.604: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb) 292s ** (umockdev-run:2418): DEBUG: 05:01:51.607: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IYB012/dev/bus/usb/003/009 292s ** (umockdev-run:2418): DEBUG: 05:01:51.607: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 292s ** (umockdev-run:2418): DEBUG: 05:01:51.608: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 292s ** (umockdev-run:2418): DEBUG: 05:01:51.611: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IYB012/dev/bus/usb/003/001 292s ** (umockdev-run:2418): DEBUG: 05:01:51.611: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 292s ** (umockdev-run:2418): DEBUG: 05:01:51.611: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 292s (process:2422): libfprint-context-DEBUG: 05:01:51.719: Initializing FpContext (libfprint version 1.94.9+tod1) 292s (process:2422): libfprint-tod-DEBUG: 05:01:51.719: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.722: 69640270: ../libfprint/drivers/egismoc/egismoc.c:1597 292s (process:2422): libfprint-context-DEBUG: 05:01:51.722: No driver found for USB device 1D6B:0002 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.722: egismoc_probe enter --> 292s (process:2422): libfprint-device-DEBUG: 05:01:51.724: Device reported probe completion 292s (process:2422): libfprint-device-DEBUG: 05:01:51.724: Completing action FPI_DEVICE_ACTION_PROBE in idle! 292s (process:2422): libfprint-device-DEBUG: 05:01:51.724: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.725: Opening device 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.726: [egismoc] DEV_INIT_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.727: [egismoc] DEV_INIT_STATES entering state 1 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.727: [egismoc] DEV_INIT_STATES entering state 2 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.728: [egismoc] DEV_INIT_STATES entering state 3 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.729: [egismoc] DEV_INIT_STATES entering state 4 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.729: [egismoc] DEV_INIT_STATES entering state 5 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.729: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.729: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.729: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.730: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.730: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.730: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.730: Firmware version callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.730: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.730: Device firmware version is 9050.6.4.67 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.730: [egismoc] DEV_INIT_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.730: Task SSM done 292s (process:2422): libfprint-device-DEBUG: 05:01:51.730: Device reported open completion 292s (process:2422): libfprint-device-DEBUG: 05:01:51.731: Completing action FPI_DEVICE_ACTION_OPEN in idle! 292s (process:2422): libfprint-device-DEBUG: 05:01:51.731: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.731: List 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.731: [egismoc] LIST_STATES entering state 0 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.731: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.731: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.731: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.732: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.732: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.732: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.732: List callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.733: Device fingerprint 1: FP1-00000000-2-00000000-nobody 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.733: Number of currently enrolled fingerprints on the device is 1 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.733: [egismoc] LIST_STATES entering state 1 292s (process:2422): libfprint-device-DEBUG: 05:01:51.733: Device reported listing completion 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.733: [egismoc] LIST_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.733: Task SSM done 292s (process:2422): libfprint-device-DEBUG: 05:01:51.733: Completing action FPI_DEVICE_ACTION_LIST in idle! 292s (process:2422): libfprint-device-DEBUG: 05:01:51.733: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.733: Clear storage 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.733: [egismoc] DELETE_STATES entering state 0 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.733: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.733: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.733: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.734: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.734: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.734: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.734: List callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.734: Device fingerprint 1: FP1-00000000-2-00000000-nobody 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.734: Number of currently enrolled fingerprints on the device is 1 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.734: [egismoc] DELETE_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.734: Get delete command 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.734: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.734: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.734: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.735: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.735: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.735: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.735: Delete callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.735: Response prefix valid: yes 292s (process:2422): libfprint-device-DEBUG: 05:01:51.735: Device reported deletion completion 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.735: [egismoc] DELETE_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.735: Task SSM done 292s (process:2422): libfprint-device-DEBUG: 05:01:51.735: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 292s (process:2422): libfprint-device-DEBUG: 05:01:51.735: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.736: List 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.736: [egismoc] LIST_STATES entering state 0 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.736: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.736: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.736: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.736: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.737: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.737: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.737: List callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.737: Number of currently enrolled fingerprints on the device is 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.737: [egismoc] LIST_STATES entering state 1 292s (process:2422): libfprint-device-DEBUG: 05:01:51.737: Device reported listing completion 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.737: [egismoc] LIST_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.737: Task SSM done 292s (process:2422): libfprint-device-DEBUG: 05:01:51.737: Completing action FPI_DEVICE_ACTION_LIST in idle! 292s (process:2422): libfprint-device-DEBUG: 05:01:51.737: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 292s (process:2422): libfprint-device-DEBUG: 05:01:51.738: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.738: Enroll 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.738: [egismoc] ENROLL_STATES entering state 0 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.738: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.738: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.738: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.738: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.739: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.739: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.739: List callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.739: Number of currently enrolled fingerprints on the device is 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.739: [egismoc] ENROLL_STATES entering state 1 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.739: [egismoc] ENROLL_STATES entering state 2 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.739: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.739: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.740: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.740: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.741: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.741: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.741: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.741: [egismoc] ENROLL_STATES entering state 3 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.741: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.741: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.741: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.741: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.742: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.742: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.742: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.742: [egismoc] ENROLL_STATES entering state 4 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.742: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.742: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.743: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.743: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.743: [egismoc] ENROLL_STATES entering state 5 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.743: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.743: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.743: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.743: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.744: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.744: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.744: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.744: [egismoc] ENROLL_STATES entering state 6 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.744: Get check command 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.744: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.744: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.744: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.744: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.745: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.745: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.745: Enroll check callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.745: Response suffix valid: yes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.745: [egismoc] ENROLL_STATES entering state 7 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.745: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.745: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.745: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.745: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.746: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.746: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.746: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.746: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.746: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.746: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.746: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.747: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.747: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.747: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.747: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.747: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.747: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.747: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.747: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.748: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.748: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.748: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.748: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.748: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.748: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.748: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.749: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.749: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.749: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.749: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.749: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.749: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.750: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.750: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.750: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.750: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.750: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.750: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.750: Partial capture successful. Please touch the sensor again (1/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.750: Device reported enroll progress, reported 1 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.750: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.750: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.750: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.750: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.751: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.751: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.752: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.752: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.752: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.752: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.752: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.752: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.752: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.753: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.753: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.753: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.753: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.753: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.753: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.753: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.754: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.754: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.754: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.754: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.754: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.754: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.755: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.755: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.755: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.755: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.755: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.755: Partial capture successful. Please touch the sensor again (2/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.755: Device reported enroll progress, reported 2 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.755: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.755: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.755: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.755: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.756: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.756: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.756: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.756: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.756: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.756: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.756: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.756: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.757: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.758: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.758: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.758: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.758: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.758: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.758: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.758: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.758: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.758: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.758: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.758: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.758: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.759: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.759: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.759: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.759: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.759: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.759: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.759: Partial capture successful. Please touch the sensor again (3/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.759: Device reported enroll progress, reported 3 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.759: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.759: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.759: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.759: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.760: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.761: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.761: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.761: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.761: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.761: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.761: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.761: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.761: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.762: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.762: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.762: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.762: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.762: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.762: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.762: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.762: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.762: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.762: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.762: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.763: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.763: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.764: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.764: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.764: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.764: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.764: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.764: Partial capture successful. Please touch the sensor again (4/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.764: Device reported enroll progress, reported 4 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.764: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.764: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.764: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.764: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.764: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.765: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.765: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.765: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.765: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.765: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.765: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.765: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.765: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.766: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.766: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.766: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.766: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.766: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.766: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.766: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.767: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.767: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.767: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.767: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.767: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.767: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.768: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.768: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.768: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.768: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.768: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.768: Partial capture successful. Please touch the sensor again (5/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.768: Device reported enroll progress, reported 5 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.768: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.768: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.768: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.768: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.768: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.769: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.769: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.769: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.769: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.769: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.769: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.769: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.770: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.770: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.770: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.770: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.770: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.770: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.770: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.771: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.771: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.771: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.771: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.771: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.771: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.771: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.772: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.772: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.772: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.772: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.772: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.772: Partial capture successful. Please touch the sensor again (6/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.772: Device reported enroll progress, reported 6 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.772: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.772: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.772: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.772: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.773: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.773: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.773: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.773: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.773: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.773: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.773: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.773: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.774: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.774: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.774: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.774: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.774: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.774: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.774: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.775: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.775: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.775: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.775: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.775: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.775: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.776: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.776: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.776: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.776: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.776: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.776: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.776: Partial capture successful. Please touch the sensor again (7/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.776: Device reported enroll progress, reported 7 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.777: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.777: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.777: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.777: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.777: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.778: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.778: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.778: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.778: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.778: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.778: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.778: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.778: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.779: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.779: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.779: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.779: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.779: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.779: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.780: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.780: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.780: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.780: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.780: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.780: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.780: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.781: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.781: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.781: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.781: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.781: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.781: Partial capture successful. Please touch the sensor again (8/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.781: Device reported enroll progress, reported 8 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.781: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.781: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.781: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.781: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.782: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.783: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.783: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.783: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.783: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.783: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.783: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.783: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.783: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.784: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.784: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.784: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.784: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.784: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.784: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.784: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.784: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.784: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.784: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.785: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.785: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.785: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.786: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.786: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.786: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.786: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.786: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.786: Partial capture successful. Please touch the sensor again (9/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.786: Device reported enroll progress, reported 9 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.786: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.786: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.786: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.786: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.787: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.787: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.787: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.787: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.787: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.787: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.787: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.787: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.788: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.788: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.788: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.788: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.788: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.788: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.788: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.789: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.789: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.789: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.789: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.789: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.789: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.789: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.790: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.790: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.790: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.790: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.790: Response suffix valid: NO 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.790: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.790: Response suffix valid: yes 292s (process:2422): libfprint-device-DEBUG: 05:01:51.790: Device reported enroll progress, reported 9 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.790: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.790: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.790: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.790: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.791: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.791: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.791: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.791: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.791: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.791: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.791: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.791: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.792: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.792: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.792: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.792: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.792: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.792: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.792: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.793: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.793: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.793: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.793: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.793: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.793: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.793: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.794: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.794: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.794: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.794: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.794: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.794: Partial capture successful. Please touch the sensor again (10/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.794: Device reported enroll progress, reported 10 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.794: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.794: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.794: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.794: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.795: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.795: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.795: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.795: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.795: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.795: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.795: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.795: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.796: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.797: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.797: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.797: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.797: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.797: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.797: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.797: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.797: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.797: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.797: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.797: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.798: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.799: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.799: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.799: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.799: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.799: Response suffix valid: NO 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.799: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.799: Response suffix valid: yes 292s (process:2422): libfprint-device-DEBUG: 05:01:51.799: Device reported enroll progress, reported 10 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.799: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.799: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.799: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.799: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.799: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.800: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.800: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.800: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.800: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.800: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.800: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.800: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.800: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.801: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.801: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.801: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.801: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.801: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.801: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.801: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.801: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.801: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.801: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.801: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.801: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.802: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.803: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.803: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.803: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.803: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.803: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.803: Partial capture successful. Please touch the sensor again (11/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.803: Device reported enroll progress, reported 11 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.803: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.803: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.803: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.803: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.803: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.804: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.804: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.804: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.804: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.804: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.804: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.804: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.804: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.805: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.805: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.805: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.805: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.805: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.805: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.806: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.806: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.806: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.806: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.806: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.806: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.806: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.807: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.807: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.807: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.807: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.807: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.807: Partial capture successful. Please touch the sensor again (12/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.807: Device reported enroll progress, reported 12 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.807: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.807: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.807: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.807: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.807: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.808: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.808: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.808: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.808: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.808: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.808: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.808: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.808: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.809: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.809: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.809: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.809: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.809: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.809: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.810: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.810: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.810: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.810: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.810: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.810: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.810: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.811: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.811: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.811: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.811: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.811: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.811: Partial capture successful. Please touch the sensor again (13/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.811: Device reported enroll progress, reported 13 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.811: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.811: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.811: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.811: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.811: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.812: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.812: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.812: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.812: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.812: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.812: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.812: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.813: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.813: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.813: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.813: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.813: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.813: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.814: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.814: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.814: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.814: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.814: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.814: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.814: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.815: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.815: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.815: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.815: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.815: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.815: Partial capture successful. Please touch the sensor again (14/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.815: Device reported enroll progress, reported 14 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.815: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.815: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.815: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.815: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.816: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.816: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.816: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.816: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.816: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.816: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.816: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.816: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.817: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.817: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.817: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.817: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.818: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.818: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.818: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.818: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.818: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.818: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.818: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.818: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.818: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.818: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.819: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.819: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.819: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.819: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.819: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.819: Partial capture successful. Please touch the sensor again (15/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.819: Device reported enroll progress, reported 15 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.819: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.819: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.819: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.819: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.820: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.820: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.820: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.820: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.820: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.820: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.820: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.820: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.821: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.822: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.822: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.822: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.822: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.822: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.822: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.822: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.822: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.822: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.822: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.822: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.822: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.823: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.823: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.823: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.823: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.823: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.823: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.823: Partial capture successful. Please touch the sensor again (16/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.823: Device reported enroll progress, reported 16 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.823: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.823: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.823: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.823: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.824: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.824: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.825: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.825: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.825: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.825: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.825: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.825: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.825: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.826: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.826: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.826: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.826: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.826: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.826: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.826: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.826: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.826: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.827: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.827: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.827: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.827: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.828: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.828: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.828: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.828: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.828: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.828: Partial capture successful. Please touch the sensor again (17/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.828: Device reported enroll progress, reported 17 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.828: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.828: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.828: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.828: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.828: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.829: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.829: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.829: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.829: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.829: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.829: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.829: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.830: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.831: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.831: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.831: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.831: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.831: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.831: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.831: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.831: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.831: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.831: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.831: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.831: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.832: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.833: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.833: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.833: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.833: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.833: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.833: Partial capture successful. Please touch the sensor again (18/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.833: Device reported enroll progress, reported 18 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.833: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.833: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.833: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.833: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.834: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.834: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.834: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.834: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.834: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.834: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.834: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.834: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.835: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.836: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.836: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.836: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.836: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.836: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.836: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.836: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.836: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.836: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.836: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.836: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.836: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.837: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.838: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.838: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.838: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.838: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.838: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.838: Partial capture successful. Please touch the sensor again (19/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.838: Device reported enroll progress, reported 19 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.838: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.838: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.838: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.838: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-device-DEBUG: 05:01:51.838: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.839: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.839: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.839: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.839: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.839: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.839: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.839: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.839: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.840: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.841: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.841: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.841: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.841: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.841: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.841: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.841: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.841: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.841: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.841: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.841: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.841: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.842: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.843: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.843: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.843: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.843: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.843: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.843: Partial capture successful. Please touch the sensor again (20/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.843: Device reported enroll progress, reported 20 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.843: [egismoc] ENROLL_STATES entering state 12 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.843: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.843: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.843: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.843: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.844: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.844: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.844: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.844: [egismoc] ENROLL_STATES entering state 13 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.844: New fingerprint ID: FP1-00000000-2-00000000-nobody 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.844: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.844: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.844: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.845: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.845: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.845: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.845: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.845: [egismoc] ENROLL_STATES entering state 14 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.845: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.845: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.845: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.846: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.847: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.847: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.847: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.847: [egismoc] ENROLL_STATES entering state 15 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.847: Enrollment was successful! 292s (process:2422): libfprint-device-DEBUG: 05:01:51.847: Device reported enroll completion 292s (process:2422): libfprint-device-DEBUG: 05:01:51.847: Device reported finger status change: FP_FINGER_STATUS_NONE 292s (process:2422): libfprint-device-DEBUG: 05:01:51.847: Print for finger FP_FINGER_LEFT_INDEX enrolled 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.847: [egismoc] ENROLL_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.847: Task SSM done 292s (process:2422): libfprint-device-DEBUG: 05:01:51.847: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 292s (process:2422): libfprint-device-DEBUG: 05:01:51.847: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.847: List 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.847: [egismoc] LIST_STATES entering state 0 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.847: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.847: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.847: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.847: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.848: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.848: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.848: List callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.848: Device fingerprint 1: FP1-00000000-2-00000000-nobody 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.848: Number of currently enrolled fingerprints on the device is 1 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.848: [egismoc] LIST_STATES entering state 1 292s (process:2422): libfprint-device-DEBUG: 05:01:51.848: Device reported listing completion 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.848: [egismoc] LIST_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.848: Task SSM done 292s (process:2422): libfprint-device-DEBUG: 05:01:51.848: Completing action FPI_DEVICE_ACTION_LIST in idle! 292s (process:2422): libfprint-device-DEBUG: 05:01:51.849: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 292s (process:2422): libfprint-device-DEBUG: 05:01:51.849: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.849: Identify or Verify 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.849: [egismoc] IDENTIFY_STATES entering state 0 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.849: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.849: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.849: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.850: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.850: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.850: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.850: List callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.850: Device fingerprint 1: FP1-00000000-2-00000000-nobody 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.850: Number of currently enrolled fingerprints on the device is 1 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.850: [egismoc] IDENTIFY_STATES entering state 1 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.850: [egismoc] IDENTIFY_STATES entering state 2 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.850: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.850: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.850: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.851: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.852: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.852: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.852: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.852: [egismoc] IDENTIFY_STATES entering state 3 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.852: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.852: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.852: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.852: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.853: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.853: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.853: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.853: [egismoc] IDENTIFY_STATES entering state 4 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.853: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.853: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.854: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.854: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.854: [egismoc] IDENTIFY_STATES entering state 5 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.854: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.854: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.854: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.854: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.855: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.855: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.855: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.855: [egismoc] IDENTIFY_STATES entering state 6 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.855: Get check command 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.855: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.855: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.855: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.856: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.856: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.856: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.856: Identify check callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.856: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.856: Identify successful for: FP1-00000000-2-00000000-nobody 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.856: Verifying against: FP1-00000000-2-00000000-nobody 292s (process:2422): libfprint-device-DEBUG: 05:01:51.856: Device reported verify result 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.856: [egismoc] IDENTIFY_STATES entering state 7 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.856: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.856: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.856: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.857: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.857: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.857: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.857: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.857: [egismoc] IDENTIFY_STATES entering state 8 292s (process:2422): libfprint-device-DEBUG: 05:01:51.857: Device reported verify completion 292s (process:2422): libfprint-device-DEBUG: 05:01:51.858: Device reported finger status change: FP_FINGER_STATUS_NONE 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.858: [egismoc] IDENTIFY_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.858: Task SSM done 292s (process:2422): libfprint-device-DEBUG: 05:01:51.858: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 292s (process:2422): libfprint-device-DEBUG: 05:01:51.858: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 292s (process:2422): libfprint-device-DEBUG: 05:01:51.858: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.858: Identify or Verify 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.858: [egismoc] IDENTIFY_STATES entering state 0 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.858: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.858: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.858: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.859: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.859: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.860: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.860: List callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.860: Device fingerprint 1: FP1-00000000-2-00000000-nobody 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.860: Number of currently enrolled fingerprints on the device is 1 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.860: [egismoc] IDENTIFY_STATES entering state 1 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.860: [egismoc] IDENTIFY_STATES entering state 2 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.860: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.860: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.860: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.860: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.861: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.861: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.861: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.861: [egismoc] IDENTIFY_STATES entering state 3 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.861: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.861: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.861: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.862: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.862: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.862: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.862: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.862: [egismoc] IDENTIFY_STATES entering state 4 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.862: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.862: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.863: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.863: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.863: [egismoc] IDENTIFY_STATES entering state 5 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.863: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.863: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.863: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.864: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.864: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.864: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.864: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.864: [egismoc] IDENTIFY_STATES entering state 6 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.864: Get check command 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.864: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.864: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.864: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.865: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.866: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.866: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.866: Identify check callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.866: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.866: Identify successful for: FP1-00000000-2-00000000-nobody 292s (process:2422): libfprint-device-DEBUG: 05:01:51.866: Device reported identify result 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.866: [egismoc] IDENTIFY_STATES entering state 7 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.866: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.866: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.866: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.866: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.867: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.867: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.867: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.867: [egismoc] IDENTIFY_STATES entering state 8 292s (process:2422): libfprint-device-DEBUG: 05:01:51.867: Device reported identify completion 292s (process:2422): libfprint-device-DEBUG: 05:01:51.867: Device reported finger status change: FP_FINGER_STATUS_NONE 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.867: [egismoc] IDENTIFY_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.867: Task SSM done 292s (process:2422): libfprint-device-DEBUG: 05:01:51.867: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 292s (process:2422): libfprint-device-DEBUG: 05:01:51.867: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 292s (process:2422): libfprint-device-DEBUG: 05:01:51.868: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.868: Enroll 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.868: [egismoc] ENROLL_STATES entering state 0 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.868: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.868: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.868: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.868: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.869: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.869: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.869: List callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.869: Device fingerprint 1: FP1-00000000-2-00000000-nobody 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.869: Number of currently enrolled fingerprints on the device is 1 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.869: [egismoc] ENROLL_STATES entering state 1 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.869: [egismoc] ENROLL_STATES entering state 2 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.870: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.870: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.870: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.870: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.871: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.871: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.871: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.871: [egismoc] ENROLL_STATES entering state 3 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.871: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.871: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.871: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.871: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.872: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.872: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.872: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.872: [egismoc] ENROLL_STATES entering state 4 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.872: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.873: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.873: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.873: [egismoc] ENROLL_STATES entering state 5 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.873: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.873: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.873: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.873: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.874: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.874: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.874: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.874: [egismoc] ENROLL_STATES entering state 6 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.874: Get check command 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.874: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.874: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.874: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.874: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.875: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.875: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.875: Enroll check callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.875: Response suffix valid: NO 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.875: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.875: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.875: Task SSM done 292s (process:2422): libfprint-device-DEBUG: 05:01:51.875: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 292s (process:2422): libfprint-device-DEBUG: 05:01:51.875: Device reported enroll completion 292s (process:2422): libfprint-device-DEBUG: 05:01:51.875: Device reported finger status change: FP_FINGER_STATUS_NONE 292s (process:2422): libfprint-device-DEBUG: 05:01:51.875: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 292s (process:2422): libfprint-device-DEBUG: 05:01:51.875: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.875: List 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.875: [egismoc] LIST_STATES entering state 0 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.875: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.875: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.875: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.876: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.877: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.877: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.877: List callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.877: Device fingerprint 1: FP1-00000000-2-00000000-nobody 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.877: Number of currently enrolled fingerprints on the device is 1 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.877: [egismoc] LIST_STATES entering state 1 292s (process:2422): libfprint-device-DEBUG: 05:01:51.877: Device reported listing completion 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.877: [egismoc] LIST_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.877: Task SSM done 292s (process:2422): libfprint-device-DEBUG: 05:01:51.877: Completing action FPI_DEVICE_ACTION_LIST in idle! 292s (process:2422): libfprint-device-DEBUG: 05:01:51.877: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 292s (process:2422): libfprint-device-DEBUG: 05:01:51.877: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.877: Enroll 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.877: [egismoc] ENROLL_STATES entering state 0 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.878: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.878: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.878: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.878: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.879: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.879: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.879: List callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.879: Device fingerprint 1: FP1-00000000-2-00000000-nobody 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.879: Number of currently enrolled fingerprints on the device is 1 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.879: [egismoc] ENROLL_STATES entering state 1 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.879: [egismoc] ENROLL_STATES entering state 2 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.879: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.879: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.879: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.879: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.880: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.880: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.880: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.880: [egismoc] ENROLL_STATES entering state 3 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.880: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.880: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.880: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.881: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.881: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.881: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.881: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.881: [egismoc] ENROLL_STATES entering state 4 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.882: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.882: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.882: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.882: [egismoc] ENROLL_STATES entering state 5 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.882: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.882: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.882: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.883: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.883: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.883: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.883: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.883: [egismoc] ENROLL_STATES entering state 6 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.883: Get check command 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.883: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.883: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.883: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.884: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.884: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.885: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.885: Enroll check callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.885: Response suffix valid: yes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.885: [egismoc] ENROLL_STATES entering state 7 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.885: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.885: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.885: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.885: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.886: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.886: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.886: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.886: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.886: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.886: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.886: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.886: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.887: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.887: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.887: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.887: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.887: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.887: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.887: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.888: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.888: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.888: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.888: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.888: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.888: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.888: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.889: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.889: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.889: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.889: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.889: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.889: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.889: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.890: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.890: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.890: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.890: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.890: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.890: Partial capture successful. Please touch the sensor again (1/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.890: Device reported enroll progress, reported 1 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.890: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.890: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.890: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.890: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.891: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.891: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.891: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.891: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.891: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.891: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.891: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.891: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.892: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.893: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.893: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.893: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.893: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.893: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.893: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.893: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.893: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.893: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.893: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.893: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.894: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.895: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.895: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.895: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.895: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.895: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.895: Partial capture successful. Please touch the sensor again (2/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.895: Device reported enroll progress, reported 2 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.895: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.895: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.895: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.895: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.895: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.896: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.896: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.896: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.896: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.896: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.896: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.896: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.896: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.897: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.897: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.897: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.897: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.897: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.897: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.898: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.898: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.898: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.898: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.898: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.898: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.899: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.899: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.899: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.899: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.899: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.899: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.899: Partial capture successful. Please touch the sensor again (3/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.899: Device reported enroll progress, reported 3 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.899: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.899: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.899: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.899: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.900: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.900: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.901: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.901: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.901: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.901: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.901: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.901: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.901: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.902: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.902: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.902: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.902: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.902: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.902: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.902: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.903: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.903: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.903: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.903: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.903: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.903: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.904: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.904: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.904: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.904: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.904: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.904: Partial capture successful. Please touch the sensor again (4/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.904: Device reported enroll progress, reported 4 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.904: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.904: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.904: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.904: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.904: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.905: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.905: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.905: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.905: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.905: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.905: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.905: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.906: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.906: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.906: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.906: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.906: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.906: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.906: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.907: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.907: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.907: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.907: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.907: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.907: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.907: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.908: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.908: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.908: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.908: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.908: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.908: Partial capture successful. Please touch the sensor again (5/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.908: Device reported enroll progress, reported 5 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.908: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.908: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.908: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.908: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.909: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.909: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.909: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.909: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.909: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.909: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.909: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.909: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.910: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.910: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.910: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.910: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.910: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.910: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.911: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.911: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.911: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.911: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.911: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.911: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.912: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.912: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.912: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.912: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.912: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.912: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.912: Partial capture successful. Please touch the sensor again (6/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.912: Device reported enroll progress, reported 6 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.912: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.912: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.912: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.912: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.913: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.914: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.914: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.914: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.914: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.914: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.914: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.914: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.914: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.915: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.915: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.915: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.915: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.915: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.915: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.915: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.916: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.916: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.916: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.916: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.916: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.916: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.917: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.917: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.917: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.917: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.917: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.917: Partial capture successful. Please touch the sensor again (7/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.917: Device reported enroll progress, reported 7 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.917: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.917: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.917: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.917: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.917: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.918: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.918: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.918: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.918: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.918: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.918: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.918: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.919: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.919: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.919: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.919: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.919: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.919: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.919: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.920: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.920: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.920: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.920: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.920: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.920: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.920: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.921: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.921: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.921: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.921: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.921: Response suffix valid: NO 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.921: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.921: Response suffix valid: yes 292s (process:2422): libfprint-device-DEBUG: 05:01:51.921: Device reported enroll progress, reported 7 of 20 have been completed 292s listing - device should have prints 292s clear device storage 292s clear done 292s listing - device should be empty 292s enrolling 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 1, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 2, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 3, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 4, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 5, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 6, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 7, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 8, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 9, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 10, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 10, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 11, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 12, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 13, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 14, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 15, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 16, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 17, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 18, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 19, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 20, , None, None) 292s enroll done 292s listing - device should have 1 print 292s verifying 292s verify done 292s async identifying 292s indentification_done: 292s try to enroll duplicate 292s duplicate enroll attempt done 292s listing - device should still only have 1 print 292s enroll new finger 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 1, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 2, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 3, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 4, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 5, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 6, , None, None) 292s finger status: 292s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 7, , None, None) 292s finger status: (process:2422): libfprint-SSM-DEBUG: 05:01:51.921: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.921: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.921: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.921: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.922: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.923: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.923: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.923: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.923: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.923: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.923: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.923: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.924: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.924: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.924: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.924: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.924: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.924: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.924: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.925: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.925: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.925: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.925: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.925: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.925: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.926: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.926: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.926: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.926: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.926: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.926: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.926: Partial capture successful. Please touch the sensor again (8/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.926: Device reported enroll progress, reported 8 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.927: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.927: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.927: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.927: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.927: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.928: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.928: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.928: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.928: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.928: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.928: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.928: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.928: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.929: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.929: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.929: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.929: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.929: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.930: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.930: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.930: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.930: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.930: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.930: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.930: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.931: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.931: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.931: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.931: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.931: Response suffix valid: NO 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.931: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.931: Response suffix valid: yes 292s (process:2422): libfprint-device-DEBUG: 05:01:51.931: Device reported enroll progress, reported 8 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.931: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.931: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.931: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.931: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.932: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.932: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.932: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.933: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.933: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.933: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.933: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.933: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.933: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.934: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.934: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.934: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.934: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.934: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.934: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.934: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.934: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.934: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.934: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.934: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.934: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.935: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.936: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.936: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.936: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.936: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.936: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.936: Partial capture successful. Please touch the sensor again (9/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.936: Device reported enroll progress, reported 9 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.936: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.936: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.936: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.936: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.936: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.937: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.937: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.937: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.937: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.937: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.937: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.937: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.938: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.938: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.938: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.938: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.938: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.938: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.938: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.939: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.939: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.939: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.939: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.939: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.939: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.940: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.941: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.941: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.941: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.941: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.941: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.941: Partial capture successful. Please touch the sensor again (10/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.941: Device reported enroll progress, reported 10 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.941: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.941: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.941: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.941: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.941: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.942: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.942: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.942: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.942: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.942: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.942: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.942: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.943: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.943: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.943: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.943: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.943: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.943: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.943: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.944: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.944: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.944: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.944: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.944: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.944: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.945: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.946: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.946: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.946: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.946: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.946: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.946: Partial capture successful. Please touch the sensor again (11/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.946: Device reported enroll progress, reported 11 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.946: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.946: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.946: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.946: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.946: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.947: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.947: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.947: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.947: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.947: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.947: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.947: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.948: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.949: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.949: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.949: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.949: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.949: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.949: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.950: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.950: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.950: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.950: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.950: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.950: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.950: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.951: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.951: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.951: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.951: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.951: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.951: Partial capture successful. Please touch the sensor again (12/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.951: Device reported enroll progress, reported 12 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.951: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.951: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.951: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.951: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.952: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.952: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.952: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.952: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.952: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.952: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.952: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.952: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.953: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.953: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.953: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.953: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.953: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.953: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.953: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.954: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.954: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.954: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.954: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.954: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.954: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.955: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.955: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.955: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.955: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.955: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.955: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.955: Partial capture successful. Please touch the sensor again (13/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.955: Device reported enroll progress, reported 13 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.955: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.955: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.955: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.955: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.956: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.957: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.957: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.957: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.957: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.957: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.957: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.957: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.957: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.958: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.958: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.958: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.958: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.958: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.958: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.958: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.958: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.958: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.958: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.958: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.958: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.959: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.960: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.960: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.960: Read capture callback 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.960: Response prefix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.960: Response suffix valid: yes 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.960: Partial capture successful. Please touch the sensor again (14/20) 292s (process:2422): libfprint-device-DEBUG: 05:01:51.960: Device reported enroll progress, reported 14 of 20 have been completed 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.960: [egismoc] ENROLL_STATES entering state 8 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.960: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.960: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.960: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.960: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.961: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.961: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.961: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.961: [egismoc] ENROLL_STATES entering state 9 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.961: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.961: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.961: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.962: [egismoc] CMD_STATES entering state 1 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.962: Command receive callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.962: [egismoc] CMD_STATES completed successfully 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.962: Task SSM next state callback 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.962: [egismoc] ENROLL_STATES entering state 10 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.962: Wait for finger on sensor 292s (process:2422): libfprint-device-DEBUG: 05:01:51.962: Device reported finger status change: FP_FINGER_STATUS_NEEDED 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.963: Finger on sensor callback 292s (process:2422): libfprint-device-DEBUG: 05:01:51.963: Device reported finger status change: FP_FINGER_STATUS_PRESENT 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.963: [egismoc] ENROLL_STATES entering state 11 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.963: Execute command and get response 292s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.963: Get check bytes 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.963: [egismoc] CMD_STATES entering state 0 292s (process:2422): libfprint-SSM-DEBUG: 05:01:51.964: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.964: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.964: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.964: Read capture callback 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.964: Response prefix valid: yes 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.964: Response suffix valid: yes 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.964: Partial capture successful. Please touch the sensor again (15/20) 293s (process:2422): libfprint-device-DEBUG: 05:01:51.964: Device reported enroll progress, reported 15 of 20 have been completed 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.964: [egismoc] ENROLL_STATES entering state 8 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.964: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.964: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.964: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.965: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.966: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.966: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.966: Task SSM next state callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.966: [egismoc] ENROLL_STATES entering state 9 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.966: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.966: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.966: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.966: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.967: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.967: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.967: Task SSM next state callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.967: [egismoc] ENROLL_STATES entering state 10 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.967: Wait for finger on sensor 293s (process:2422): libfprint-device-DEBUG: 05:01:51.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.967: Finger on sensor callback 293s (process:2422): libfprint-device-DEBUG: 05:01:51.967: Device reported finger status change: FP_FINGER_STATUS_PRESENT 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.967: [egismoc] ENROLL_STATES entering state 11 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.967: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.967: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.967: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.968: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.968: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.968: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.969: Read capture callback 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.969: Response prefix valid: yes 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.969: Response suffix valid: yes 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.969: Partial capture successful. Please touch the sensor again (16/20) 293s (process:2422): libfprint-device-DEBUG: 05:01:51.969: Device reported enroll progress, reported 16 of 20 have been completed 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.969: [egismoc] ENROLL_STATES entering state 8 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.969: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.969: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.969: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.969: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.970: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.970: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.970: Task SSM next state callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.970: [egismoc] ENROLL_STATES entering state 9 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.970: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.970: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.970: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.971: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.971: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.971: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.971: Task SSM next state callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.971: [egismoc] ENROLL_STATES entering state 10 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.971: Wait for finger on sensor 293s (process:2422): libfprint-device-DEBUG: 05:01:51.971: Device reported finger status change: FP_FINGER_STATUS_NEEDED 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.972: Finger on sensor callback 293s (process:2422): libfprint-device-DEBUG: 05:01:51.972: Device reported finger status change: FP_FINGER_STATUS_PRESENT 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.972: [egismoc] ENROLL_STATES entering state 11 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.972: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.972: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.972: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.972: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.973: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.973: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.973: Read capture callback 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.973: Response prefix valid: yes 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.973: Response suffix valid: yes 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.973: Partial capture successful. Please touch the sensor again (17/20) 293s (process:2422): libfprint-device-DEBUG: 05:01:51.973: Device reported enroll progress, reported 17 of 20 have been completed 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.973: [egismoc] ENROLL_STATES entering state 8 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.973: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.973: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.973: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.974: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.974: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.974: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.974: Task SSM next state callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.974: [egismoc] ENROLL_STATES entering state 9 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.974: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.974: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.974: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.975: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.975: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.975: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.975: Task SSM next state callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.975: [egismoc] ENROLL_STATES entering state 10 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.975: Wait for finger on sensor 293s (process:2422): libfprint-device-DEBUG: 05:01:51.975: Device reported finger status change: FP_FINGER_STATUS_NEEDED 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.976: Finger on sensor callback 293s (process:2422): libfprint-device-DEBUG: 05:01:51.976: Device reported finger status change: FP_FINGER_STATUS_PRESENT 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.976: [egismoc] ENROLL_STATES entering state 11 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.976: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.976: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.976: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.976: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.977: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.977: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.977: Read capture callback 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.977: Response prefix valid: yes 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.977: Response suffix valid: yes 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.977: Partial capture successful. Please touch the sensor again (18/20) 293s (process:2422): libfprint-device-DEBUG: 05:01:51.977: Device reported enroll progress, reported 18 of 20 have been completed 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.977: [egismoc] ENROLL_STATES entering state 8 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.977: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.977: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.977: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.978: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.978: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.978: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.978: Task SSM next state callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.978: [egismoc] ENROLL_STATES entering state 9 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.979: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.979: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.979: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.979: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.980: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.980: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.980: Task SSM next state callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.980: [egismoc] ENROLL_STATES entering state 10 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.980: Wait for finger on sensor 293s (process:2422): libfprint-device-DEBUG: 05:01:51.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.981: Finger on sensor callback 293s (process:2422): libfprint-device-DEBUG: 05:01:51.981: Device reported finger status change: FP_FINGER_STATUS_PRESENT 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.981: [egismoc] ENROLL_STATES entering state 11 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.981: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.981: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.981: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.981: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.982: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.982: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.982: Read capture callback 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.982: Response prefix valid: yes 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.982: Response suffix valid: yes 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.982: Partial capture successful. Please touch the sensor again (19/20) 293s (process:2422): libfprint-device-DEBUG: 05:01:51.982: Device reported enroll progress, reported 19 of 20 have been completed 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.982: [egismoc] ENROLL_STATES entering state 8 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.982: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.982: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.982: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.983: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.984: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.984: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.984: Task SSM next state callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.984: [egismoc] ENROLL_STATES entering state 9 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.984: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.984: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.984: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.984: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.985: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.985: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.985: Task SSM next state callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.985: [egismoc] ENROLL_STATES entering state 10 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.985: Wait for finger on sensor 293s (process:2422): libfprint-device-DEBUG: 05:01:51.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.985: Finger on sensor callback 293s (process:2422): libfprint-device-DEBUG: 05:01:51.985: Device reported finger status change: FP_FINGER_STATUS_PRESENT 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.985: [egismoc] ENROLL_STATES entering state 11 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.985: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.985: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.985: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.986: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.987: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.987: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.987: Read capture callback 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.987: Response prefix valid: yes 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.987: Response suffix valid: yes 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.987: Partial capture successful. Please touch the sensor again (20/20) 293s (process:2422): libfprint-device-DEBUG: 05:01:51.987: Device reported enroll progress, reported 20 of 20 have been completed 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.987: [egismoc] ENROLL_STATES entering state 12 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.987: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.987: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.987: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.987: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.988: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.988: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.988: Task SSM next state callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.988: [egismoc] ENROLL_STATES entering state 13 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.988: New fingerprint ID: FP1-00000000-7-00000000-nobody 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.988: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.988: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.988: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.989: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.989: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.989: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.989: Task SSM next state callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.989: [egismoc] ENROLL_STATES entering state 14 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.989: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.989: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.989: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.990: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.990: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.990: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.990: Task SSM next state callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.990: [egismoc] ENROLL_STATES entering state 15 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.990: Enrollment was successful! 293s (process:2422): libfprint-device-DEBUG: 05:01:51.990: Device reported enroll completion 293s (process:2422): libfprint-device-DEBUG: 05:01:51.990: Device reported finger status change: FP_FINGER_STATUS_NONE 293s (process:2422): libfprint-device-DEBUG: 05:01:51.990: Print for finger FP_FINGER_RIGHT_INDEX enrolled 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.990: [egismoc] ENROLL_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.990: Task SSM done 293s (process:2422): libfprint-device-DEBUG: 05:01:51.990: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 293s (process:2422): libfprint-device-DEBUG: 05:01:51.990: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.990: List 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.990: [egismoc] LIST_STATES entering state 0 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.990: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.991: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.991: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.991: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.992: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.992: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.992: List callback 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.992: Device fingerprint 1: FP1-00000000-2-00000000-nobody 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.992: Device fingerprint 2: FP1-00000000-7-00000000-nobody 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.992: Number of currently enrolled fingerprints on the device is 2 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.992: [egismoc] LIST_STATES entering state 1 293s (process:2422): libfprint-device-DEBUG: 05:01:51.992: Device reported listing completion 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.992: [egismoc] LIST_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.992: Task SSM done 293s (process:2422): libfprint-device-DEBUG: 05:01:51.992: Completing action FPI_DEVICE_ACTION_LIST in idle! 293s (process:2422): libfprint-device-DEBUG: 05:01:51.992: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.992: Delete 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.992: [egismoc] DELETE_STATES entering state 0 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.992: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.992: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.992: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.993: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.993: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.993: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.993: List callback 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.993: Device fingerprint 1: FP1-00000000-2-00000000-nobody 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.993: Device fingerprint 2: FP1-00000000-7-00000000-nobody 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.993: Number of currently enrolled fingerprints on the device is 2 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.993: [egismoc] DELETE_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.993: Get delete command 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.993: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.993: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.993: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.993: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.994: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.994: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.994: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.994: Delete callback 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.994: Response prefix valid: yes 293s (process:2422): libfprint-device-DEBUG: 05:01:51.994: Device reported deletion completion 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.995: [egismoc] DELETE_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.995: Task SSM done 293s (process:2422): libfprint-device-DEBUG: 05:01:51.995: Completing action FPI_DEVICE_ACTION_DELETE in idle! 293s (process:2422): libfprint-device-DEBUG: 05:01:51.995: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.995: List 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.995: [egismoc] LIST_STATES entering state 0 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.995: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.995: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.995: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.995: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.996: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.996: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.996: List callback 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.996: Device fingerprint 1: FP1-00000000-7-00000000-nobody 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.996: Number of currently enrolled fingerprints on the device is 1 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.996: [egismoc] LIST_STATES entering state 1 293s (process:2422): libfprint-device-DEBUG: 05:01:51.996: Device reported listing completion 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.996: [egismoc] LIST_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.996: Task SSM done 293s (process:2422): libfprint-device-DEBUG: 05:01:51.996: Completing action FPI_DEVICE_ACTION_LIST in idle! 293s (process:2422): libfprint-device-DEBUG: 05:01:51.996: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.996: Clear storage 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.996: [egismoc] DELETE_STATES entering state 0 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.996: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.996: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.996: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.996: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.997: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.997: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.997: List callback 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.997: Device fingerprint 1: FP1-00000000-7-00000000-nobody 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.997: Number of currently enrolled fingerprints on the device is 1 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.997: [egismoc] DELETE_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.997: Get delete command 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.997: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.997: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.997: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.997: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.998: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.998: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.998: Delete callback 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.998: Response prefix valid: yes 293s (process:2422): libfprint-device-DEBUG: 05:01:51.998: Device reported deletion completion 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.998: [egismoc] DELETE_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.998: Task SSM done 293s (process:2422): libfprint-device-DEBUG: 05:01:51.998: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 293s (process:2422): libfprint-device-DEBUG: 05:01:51.998: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.998: List 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.998: [egismoc] LIST_STATES entering state 0 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.998: Execute command and get response 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.998: Get check bytes 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.998: [egismoc] CMD_STATES entering state 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.999: [egismoc] CMD_STATES entering state 1 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.999: Command receive callback 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.999: [egismoc] CMD_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.999: List callback 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.999: Number of currently enrolled fingerprints on the device is 0 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.999: [egismoc] LIST_STATES entering state 1 293s (process:2422): libfprint-device-DEBUG: 05:01:51.999: Device reported listing completion 293s (process:2422): libfprint-SSM-DEBUG: 05:01:51.999: [egismoc] LIST_STATES completed successfully 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:51.999: Task SSM done 293s (process:2422): libfprint-device-DEBUG: 05:01:51.999: Completing action FPI_DEVICE_ACTION_LIST in idle! 293s (process:2422): libfprint-device-DEBUG: 05:01:51.999: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:52.000: Closing device 293s (process:2422): libfprint-egismoc-DEBUG: 05:01:52.000: Cancel 293s (process:2422): libfprint-device-DEBUG: 05:01:52.000: Device reported close completion 293s (process:2422): libfprint-device-DEBUG: 05:01:52.000: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 293s (process:2422): libfprint-device-DEBUG: 05:01:52.000: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 293s 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 293s finger status: 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 8, , None, None) 293s finger status: 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 293s finger status: 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 9, , None, None) 293s finger status: 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 10, , None, None) 293s finger status: 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 11, , None, None) 293s finger status: 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 12, , None, None) 293s finger status: 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 13, , None, None) 293s finger status: 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 14, , None, None) 293s finger status: 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 15, , None, None) 293s finger status: 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 16, , None, None) 293s finger status: 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 17, , None, None) 293s finger status: 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 18, , None, None) 293s finger status: 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 19, , None, None) 293s finger status: 293s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf5ddc2ffe680 (FpiDeviceEgisMoc at 0x8663aa0)>, 20, , None, None) 293s enroll new finger done 293s listing - device should have 2 prints 293s deleting first print 293s delete done 293s listing - device should only have second print 293s clear device storage 293s clear done 293s listing - device should be empty 293s ** (umockdev-run:2418): DEBUG: 05:01:52.036: umockdev.vala:154: Removing test bed /tmp/umockdev.IYB012 293s (umockdev-run:2418): GLib-DEBUG: 05:01:52.040: unsetenv() is not thread-safe and should not be used after threads are created 293s PASS: libfprint-2/driver-egismoc-0587.test 293s Running test: libfprint-2/driver-elan-cobo.test 293s ** (umockdev-run:2430): DEBUG: 05:01:52.100: umockdev.vala:127: Created udev test bed /tmp/umockdev.WQ4B22 293s ** (umockdev-run:2430): DEBUG: 05:01:52.100: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 293s ** (umockdev-run:2430): DEBUG: 05:01:52.102: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 293s ** (umockdev-run:2430): DEBUG: 05:01:52.104: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WQ4B22/dev/bus/usb/001/045 293s ** (umockdev-run:2430): DEBUG: 05:01:52.104: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 293s ** (umockdev-run:2430): DEBUG: 05:01:52.105: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 293s ** (umockdev-run:2430): DEBUG: 05:01:52.107: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WQ4B22/dev/bus/usb/001/001 293s ** (umockdev-run:2430): DEBUG: 05:01:52.107: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 293s ** (umockdev-run:2430): DEBUG: 05:01:52.108: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 293s (process:2434): libfprint-context-DEBUG: 05:01:52.218: Initializing FpContext (libfprint version 1.94.9+tod1) 293s (process:2434): libfprint-tod-DEBUG: 05:01:52.219: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 293s (process:2434): libfprint-context-DEBUG: 05:01:52.221: No driver found for USB device 1D6B:0002 293s (process:2434): libfprint-device-DEBUG: 05:01:52.221: Device reported probe completion 293s (process:2434): libfprint-device-DEBUG: 05:01:52.221: Completing action FPI_DEVICE_ACTION_PROBE in idle! 293s (process:2434): libfprint-device-DEBUG: 05:01:52.221: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.223: 70141186: ../libfprint/drivers/elan.c:908 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.223: Image device open completed 293s (process:2434): libfprint-device-DEBUG: 05:01:52.223: Device reported open completion 293s (process:2434): libfprint-device-DEBUG: 05:01:52.223: Completing action FPI_DEVICE_ACTION_OPEN in idle! 293s (process:2434): libfprint-device-DEBUG: 05:01:52.223: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 293s (process:2434): libfprint-device-DEBUG: 05:01:52.223: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.223: Activating image device 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.223: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.223: 70141962: ../libfprint/drivers/elan.c:960 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.223: 70141972: ../libfprint/drivers/elan.c:951 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.223: 70141975: ../libfprint/drivers/elan.c:892 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.223: 70141978: ../libfprint/drivers/elan.c:100 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.223: [elan] ACTIVATE_NUM_STATES entering state 0 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.223: 70141992: ../libfprint/drivers/elan.c:820 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.224: 70142630: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.224: 70142658: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.224: 70142663: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.225: 70143330: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.225: 70143361: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.225: [elan] ACTIVATE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.225: 70143375: ../libfprint/drivers/elan.c:820 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.225: FW ver 0x0140 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.225: [elan] ACTIVATE_NUM_STATES entering state 2 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.225: 70143388: ../libfprint/drivers/elan.c:820 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.225: 70143900: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.225: 70143918: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.225: 70143924: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.226: 70144556: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.226: 70144585: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.226: [elan] ACTIVATE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.226: 70144596: ../libfprint/drivers/elan.c:820 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.226: sensor dimensions, WxH: 144x64 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.226: [elan] ACTIVATE_NUM_STATES entering state 4 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.226: 70144611: ../libfprint/drivers/elan.c:820 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.226: skipping command 0x40 0x2a for this device (for devices 0x1 but device is 0x0) 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.226: 70144618: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.226: [elan] ACTIVATE_NUM_STATES completed successfully 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.226: 70144624: ../libfprint/drivers/elan.c:881 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.226: Image device activation completed 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.226: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.226: 70144644: ../libfprint/drivers/elan.c:960 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.226: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.226: 70144652: ../libfprint/drivers/elan.c:960 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.226: 70144659: ../libfprint/drivers/elan.c:792 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.226: 70144662: ../libfprint/drivers/elan.c:100 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.226: [elan] CALIBRATE_NUM_STATES entering state 0 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.226: 70144668: ../libfprint/drivers/elan.c:691 293s (process:2434): libfprint-device-DEBUG: 05:01:52.226: Device reported finger status change: FP_FINGER_STATUS_NEEDED 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.227: 70145331: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.227: 70145345: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.227: 70145350: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.227: 70146070: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.227: 70146115: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.227: [elan] CALIBRATE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.227: 70146137: ../libfprint/drivers/elan.c:691 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.227: 70146140: ../libfprint/drivers/elan.c:156 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.227: 70146143: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.227: [elan] CALIBRATE_NUM_STATES entering state 2 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.227: 70146164: ../libfprint/drivers/elan.c:691 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.228: 70146863: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.228: 70146884: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.228: 70146889: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.229: 70147567: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.229: 70147597: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.229: [elan] CALIBRATE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.229: 70147608: ../libfprint/drivers/elan.c:691 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.229: 70147611: ../libfprint/drivers/elan.c:634 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.229: calibration mean: 8248, bg mean: 7978, delta: 270 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.229: [elan] CALIBRATE_NUM_STATES completed successfully 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.229: 70147630: ../libfprint/drivers/elan.c:776 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.229: 70147632: ../libfprint/drivers/elan.c:620 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.229: 70147635: ../libfprint/drivers/elan.c:100 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.229: [elan] CAPTURE_NUM_STATES entering state 0 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.230: 70148202: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.230: 70148226: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.230: 70148229: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.230: skipping read, not expecting anything 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.230: 70148235: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.230: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.230: 70148817: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.230: 70148834: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.230: 70148839: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.231: 70149454: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.231: 70149479: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.231: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-device-DEBUG: 05:01:52.231: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.231: Image device reported finger status: on 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.231: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.231: 70149520: ../libfprint/drivers/elan.c:960 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.231: 70150088: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.231: 70150112: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.231: 70150117: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.232: 70150798: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.232: 70150820: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.232: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.232: 70150832: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.232: 70150850: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.232: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.233: 70151574: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.233: 70151602: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.233: 70151607: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.233: 70152152: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.234: 70152185: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.234: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.234: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.234: 70152750: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.234: 70152804: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.234: 70152814: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.235: 70153373: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.235: 70153443: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.235: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.235: 70153458: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.235: 70153471: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.235: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.235: 70154157: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.236: 70154281: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.236: 70154313: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.236: 70154813: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.236: 70154916: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.236: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.236: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.237: 70155481: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.237: 70155549: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.237: 70155557: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.238: 70156199: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.238: 70156252: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.238: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.238: 70156266: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.238: 70156279: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.238: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.238: 70156867: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.238: 70156883: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.238: 70156886: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.239: 70157497: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.239: 70157521: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.239: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.239: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.239: 70158042: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.239: 70158069: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.239: 70158073: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.240: 70158783: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.240: 70158829: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.240: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.240: 70158838: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.240: 70158850: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.240: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.241: 70159435: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.241: 70159557: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.241: 70159567: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.241: 70160059: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.241: 70160087: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.241: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.241: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.242: 70160609: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.242: 70160659: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.242: 70160668: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.243: 70161248: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.243: 70161319: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.243: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.243: 70161333: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.243: 70161345: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.243: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.243: 70161996: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.243: 70162063: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.243: 70162068: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.244: 70162589: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.244: 70162626: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.244: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.244: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.245: 70163193: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.245: 70163244: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.245: 70163249: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.245: 70163937: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.245: 70163991: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.245: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.245: 70164024: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.245: 70164045: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.245: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.246: 70164658: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.246: 70164710: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.246: 70164720: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.247: 70165348: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.247: 70165380: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.247: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.247: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.247: 70165974: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.247: 70165992: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.247: 70165998: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.248: 70166742: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.248: 70166768: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.248: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.248: 70166784: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.248: 70166798: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.248: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.249: 70167426: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.249: 70167453: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.249: 70167458: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.249: 70168056: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.249: 70168082: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.249: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.249: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.250: 70168666: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.250: 70168684: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.250: 70168690: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.251: 70169341: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.251: 70169374: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.251: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.251: 70169392: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.251: 70169417: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.251: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.251: 70170021: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.251: 70170047: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.251: 70170052: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.252: 70170624: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.252: 70170644: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.252: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.252: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.253: 70171197: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.253: 70171222: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.253: 70171227: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.253: 70171888: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.253: 70171913: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.253: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.253: 70171926: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.253: 70171944: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.253: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.254: 70172874: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.254: 70172904: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.254: 70172909: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.255: 70173509: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.255: 70173537: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.255: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.255: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.255: 70174128: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.256: 70174179: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.256: 70174185: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.256: 70174775: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.256: 70174833: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.256: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.256: 70174849: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.256: 70174862: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.256: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.257: 70175494: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.257: 70175638: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.257: 70175649: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.257: 70176157: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.258: 70176188: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.258: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.258: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.258: 70176673: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.258: 70176712: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.258: 70176718: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.259: 70177338: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.259: 70177361: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.259: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.259: 70177370: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.259: 70177389: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.259: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.259: 70177998: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.259: 70178134: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.259: 70178144: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.260: 70178641: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.260: 70178732: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.260: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.260: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.261: 70179308: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.261: 70179328: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.261: 70179332: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.261: 70179924: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.261: 70180039: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.261: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.261: 70180064: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.261: 70180078: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.261: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.262: 70180646: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.262: 70180690: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.262: 70180697: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.263: 70181337: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.263: 70181394: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.263: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.263: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.263: 70181869: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.263: 70181908: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.263: 70181916: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.264: 70182531: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.264: 70182604: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.264: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.264: 70182617: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.264: 70182620: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.264: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.265: 70183234: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.265: 70183284: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.265: 70183312: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.265: 70183786: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.265: 70183833: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.265: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.265: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.266: 70184337: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.266: 70184462: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.266: 70184472: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.266: 70184941: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.266: 70185048: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.266: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.266: 70185106: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.266: 70185124: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.266: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.267: 70185841: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.267: 70185861: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.267: 70185866: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.268: 70186427: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.268: 70186453: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.268: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.268: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.268: 70187061: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.268: 70187086: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.268: 70187091: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.269: 70187779: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.269: 70187805: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.269: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.269: 70187821: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.269: 70187836: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.269: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.270: 70188437: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.270: 70188464: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.270: 70188470: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.270: 70189047: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.270: 70189073: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.270: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-image_device-DEBUG: 05:01:52.270: Image device reported finger status: on 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.271: 70189648: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.271: 70189669: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.271: 70189675: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.272: 70190344: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.272: 70190378: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.272: [elan] CAPTURE_NUM_STATES entering state 3 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.272: 70190389: ../libfprint/drivers/elan.c:203 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.272: 70190404: ../libfprint/drivers/elan.c:118 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.272: [elan] CAPTURE_NUM_STATES entering state 1 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.272: 70191023: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.272: 70191049: ../libfprint/drivers/elan.c:366 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.272: 70191056: ../libfprint/drivers/elan.c:379 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.273: 70191650: ../libfprint/drivers/elan.c:346 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.273: 70191673: ../libfprint/drivers/elan.c:335 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.273: [elan] CAPTURE_NUM_STATES entering state 2 293s (process:2434): libfprint-SSM-DEBUG: 05:01:52.273: [elan] CAPTURE_NUM_STATES completed successfully 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.273: 70191695: ../libfprint/drivers/elan.c:586 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.273: 70191698: ../libfprint/drivers/elan.c:315 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.273: 70191704: ../libfprint/drivers/elan.c:272 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.274: 70192482: ../libfprint/drivers/elan.c:272 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.275: 70193220: ../libfprint/drivers/elan.c:272 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.275: 70193987: ../libfprint/drivers/elan.c:272 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.276: 70194732: ../libfprint/drivers/elan.c:272 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.277: 70195486: ../libfprint/drivers/elan.c:272 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.278: 70196214: ../libfprint/drivers/elan.c:272 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.278: 70196944: ../libfprint/drivers/elan.c:272 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.279: 70197810: ../libfprint/drivers/elan.c:272 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.280: 70198552: ../libfprint/drivers/elan.c:272 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.281: 70199274: ../libfprint/drivers/elan.c:272 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.281: 70199998: ../libfprint/drivers/elan.c:272 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.282: 70200914: ../libfprint/drivers/elan.c:272 293s (process:2434): libfprint-elan-DEBUG: 05:01:52.283: 70201652: ../libfprint/drivers/elan.c:272 293s (process:2434): libfprint-assembling-DEBUG: 05:01:52.512: calc delta completed in 0.228238 secs 293s (process:2434): libfprint-assembling-DEBUG: 05:01:52.745: calc delta completed in 0.232544 secs 293s (process:2434): libfprint-assembling-DEBUG: 05:01:52.745: errors: 133465 rev: 143589 294s (process:2434): libfprint-assembling-DEBUG: 05:01:52.976: calc delta completed in 0.230862 secs 294s (process:2434): libfprint-assembling-DEBUG: 05:01:52.976: height is 225 294s (process:2434): libfprint-image_device-DEBUG: 05:01:52.977: Image device captured an image 294s (process:2434): libfprint-image_device-DEBUG: 05:01:52.977: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.977: 70895778: ../libfprint/drivers/elan.c:960 294s (process:2434): libfprint-device-DEBUG: 05:01:52.977: Device reported finger status change: FP_FINGER_STATUS_PRESENT 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.977: 70895792: ../libfprint/drivers/elan.c:507 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.977: 70895796: ../libfprint/drivers/elan.c:100 294s (process:2434): libfprint-SSM-DEBUG: 05:01:52.977: [elan] STOP_CAPTURE_NUM_STATES entering state 0 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.977: 70895809: ../libfprint/drivers/elan.c:466 294s (process:2434): libfprint-device-DEBUG: 05:01:52.979: Updated temperature model after 0.76 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.979: 70897969: ../libfprint/drivers/elan.c:346 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.979: 70897987: ../libfprint/drivers/elan.c:366 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.979: 70897991: ../libfprint/drivers/elan.c:379 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.979: skipping read, not expecting anything 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.979: 70897999: ../libfprint/drivers/elan.c:335 294s (process:2434): libfprint-SSM-DEBUG: 05:01:52.979: [elan] STOP_CAPTURE_NUM_STATES completed successfully 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.979: 70898026: ../libfprint/drivers/elan.c:483 294s (process:2434): libfprint-device-DEBUG: 05:01:52.979: Device reported finger status change: FP_FINGER_STATUS_NONE 294s (process:2434): libfprint-image_device-DEBUG: 05:01:52.979: Image device reported finger status: off 294s (process:2434): libfprint-image_device-DEBUG: 05:01:52.979: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.979: 70898054: ../libfprint/drivers/elan.c:960 294s (process:2434): libfprint-image_device-DEBUG: 05:01:52.979: Deactivating image device 294s (process:2434): libfprint-image_device-DEBUG: 05:01:52.979: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.979: 70898066: ../libfprint/drivers/elan.c:960 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.979: 70898069: ../libfprint/drivers/elan.c:975 294s (process:2434): libfprint-image_device-DEBUG: 05:01:52.979: Image device deactivation completed 294s (process:2434): libfprint-image_device-DEBUG: 05:01:52.979: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.979: 70898082: ../libfprint/drivers/elan.c:960 294s (process:2434): libfprint-image-DEBUG: 05:01:52.995: Minutiae scan completed in 0.017123 secs 294s (process:2434): libfprint-device-DEBUG: 05:01:52.995: Device reported capture completion 294s (process:2434): libfprint-device-DEBUG: 05:01:52.995: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 294s (process:2434): libfprint-device-DEBUG: 05:01:52.995: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.995: 70913447: ../libfprint/drivers/elan.c:939 294s (process:2434): libfprint-elan-DEBUG: 05:01:52.995: 70913456: ../libfprint/drivers/elan.c:100 294s (process:2434): libfprint-image_device-DEBUG: 05:01:52.995: Image device close completed 294s (process:2434): libfprint-device-DEBUG: 05:01:52.995: Device reported close completion 294s (process:2434): libfprint-device-DEBUG: 05:01:52.995: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 294s (process:2434): libfprint-device-DEBUG: 05:01:52.995: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 294s ** (umockdev-run:2430): DEBUG: 05:01:53.116: umockdev.vala:154: Removing test bed /tmp/umockdev.WQ4B22 294s (umockdev-run:2430): GLib-DEBUG: 05:01:53.120: unsetenv() is not thread-safe and should not be used after threads are created 294s Comparing PNGs /tmp/libfprint-umockdev-test-qqr92wdf/capture.png and /usr/share/installed-tests/libfprint-2/elan-cobo/capture.png 294s PASS: libfprint-2/driver-elan-cobo.test 294s Running test: libfprint-2/driver-realtek.test 294s ** (umockdev-run:2443): DEBUG: 05:01:53.202: umockdev.vala:127: Created udev test bed /tmp/umockdev.EX5D22 294s ** (umockdev-run:2443): DEBUG: 05:01:53.202: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-8 294s ** (umockdev-run:2443): DEBUG: 05:01:53.204: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-8 (subsystem usb) 294s ** (umockdev-run:2443): DEBUG: 05:01:53.207: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.EX5D22/dev/bus/usb/001/025 294s ** (umockdev-run:2443): DEBUG: 05:01:53.207: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 294s ** (umockdev-run:2443): DEBUG: 05:01:53.208: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 294s ** (umockdev-run:2443): DEBUG: 05:01:53.210: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.EX5D22/dev/bus/usb/001/001 294s ** (umockdev-run:2443): DEBUG: 05:01:53.210: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 294s ** (umockdev-run:2443): DEBUG: 05:01:53.210: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 294s (process:2447): libfprint-context-DEBUG: 05:01:53.327: Initializing FpContext (libfprint version 1.94.9+tod1) 294s (process:2447): libfprint-tod-DEBUG: 05:01:53.327: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 294s (process:2447): libfprint-context-DEBUG: 05:01:53.330: No driver found for USB device 1D6B:0002 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.330: 71248654: ../libfprint/drivers/realtek/realtek.c:1224 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.333: Device name: Realtek USB2.0 Finger Print Bridge 294s (process:2447): libfprint-device-DEBUG: 05:01:53.333: Device reported probe completion 294s (process:2447): libfprint-device-DEBUG: 05:01:53.333: Completing action FPI_DEVICE_ACTION_PROBE in idle! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.334: Not updating temperature model, device can run continuously! 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.335: 71253424: ../libfprint/drivers/realtek/realtek.c:1269 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.335: [realtek] Init entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.336: [realtek] Init entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.336: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.337: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.337: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.337: [realtek] Init entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.337: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.338: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.338: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.339: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.339: [realtek] Init completed successfully 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.339: Init complete! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.339: Device reported open completion 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.340: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-device-DEBUG: 05:01:53.340: Completing action FPI_DEVICE_ACTION_OPEN in idle! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.340: Not updating temperature model, device can run continuously! 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.340: 71258470: ../libfprint/drivers/realtek/realtek.c:1332 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.340: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.340: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.340: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.341: Successfully cleared storage 294s (process:2447): libfprint-device-DEBUG: 05:01:53.341: Device reported deletion completion 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.341: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-device-DEBUG: 05:01:53.341: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.341: Not updating temperature model, device can run continuously! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.342: Not updating temperature model, device can run continuously! 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.342: 71260525: ../libfprint/drivers/realtek/realtek.c:1201 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.342: [realtek] Enroll entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.342: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.343: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.343: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.344: [realtek] Enroll entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.344: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.345: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.345: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.345: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.345: [realtek] Enroll entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.345: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.346: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.346: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.346: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.347: [realtek] Enroll entering state 3 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.347: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.347: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.348: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.348: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.349: Device reported finger status change: FP_FINGER_STATUS_PRESENT 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.349: [realtek] Enroll entering state 4 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.349: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.349: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.350: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.350: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.351: Device reported finger status change: FP_FINGER_STATUS_NONE 294s (process:2447): libfprint-device-DEBUG: 05:01:53.351: Device reported enroll progress, reported 1 of 8 have been completed 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.351: [realtek] Enroll entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.351: Device reported finger status change: FP_FINGER_STATUS_NEEDED 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.351: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.352: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.352: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.352: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.353: [realtek] Enroll entering state 3 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.353: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.353: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.353: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.354: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.354: Device reported finger status change: FP_FINGER_STATUS_PRESENT 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.354: [realtek] Enroll entering state 4 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.354: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.355: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.355: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.355: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.356: Device reported finger status change: FP_FINGER_STATUS_NONE 294s (process:2447): libfprint-device-DEBUG: 05:01:53.356: Device reported enroll progress, reported 2 of 8 have been completed 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.356: [realtek] Enroll entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.356: Device reported finger status change: FP_FINGER_STATUS_NEEDED 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.356: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.356: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.356: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.356: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.357: [realtek] Enroll entering state 3 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.357: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.357: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.357: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.358: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.358: Device reported finger status change: FP_FINGER_STATUS_PRESENT 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.358: [realtek] Enroll entering state 4 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.358: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.359: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.359: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.360: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.360: Device reported finger status change: FP_FINGER_STATUS_NONE 294s (process:2447): libfprint-device-DEBUG: 05:01:53.360: Device reported enroll progress, reported 3 of 8 have been completed 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.360: [realtek] Enroll entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.360: Device reported finger status change: FP_FINGER_STATUS_NEEDED 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.360: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.361: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.361: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.361: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.361: [realtek] Enroll entering state 3 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.361: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.362: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.362: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.362: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.363: Device reported finger status change: FP_FINGER_STATUS_PRESENT 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.363: [realtek] Enroll entering state 4 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.363: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.363: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.363: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.364: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.364: Device reported finger status change: FP_FINGER_STATUS_NONE 294s (process:2447): libfprint-device-DEBUG: 05:01:53.364: Device reported enroll progress, reported 4 of 8 have been completed 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.364: [realtek] Enroll entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.364: Device reported finger status change: FP_FINGER_STATUS_NEEDED 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.364: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.365: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.365: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.365: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.365: [realtek] Enroll entering state 3 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.365: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.366: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.366: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.367: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.367: Device reported finger status change: FP_FINGER_STATUS_PRESENT 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.367: [realtek] Enroll entering state 4 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.367: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.367: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.368: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.368: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.369: Device reported finger status change: FP_FINGER_STATUS_NONE 294s (process:2447): libfprint-device-DEBUG: 05:01:53.369: Device reported enroll progress, reported 5 of 8 have been completed 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.369: [realtek] Enroll entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.369: Device reported finger status change: FP_FINGER_STATUS_NEEDED 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.369: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.369: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.369: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.369: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.370: [realtek] Enroll entering state 3 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.370: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.370: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.370: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.371: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.371: Device reported finger status change: FP_FINGER_STATUS_PRESENT 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.371: [realtek] Enroll entering state 4 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.371: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.371: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.372: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.372: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.373: Device reported finger status change: FP_FINGER_STATUS_NONE 294s (process:2447): libfprint-device-DEBUG: 05:01:53.373: Device reported enroll progress, reported 6 of 8 have been completed 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.373: [realtek] Enroll entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.373: Device reported finger status change: FP_FINGER_STATUS_NEEDED 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.373: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.373: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.373: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.373: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.374: [realtek] Enroll entering state 3 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.374: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.374: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.374: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.375: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.375: Device reported finger status change: FP_FINGER_STATUS_PRESENT 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.375: [realtek] Enroll entering state 4 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.375: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.376: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.376: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.377: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.377: Device reported finger status change: FP_FINGER_STATUS_NONE 294s (process:2447): libfprint-device-DEBUG: 05:01:53.377: Device reported enroll progress, reported 7 of 8 have been completed 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.377: [realtek] Enroll entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.377: Device reported finger status change: FP_FINGER_STATUS_NEEDED 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.377: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.377: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.378: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.378: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.378: [realtek] Enroll entering state 3 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.378: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.379: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.379: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.380: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.380: Device reported finger status change: FP_FINGER_STATUS_PRESENT 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.380: [realtek] Enroll entering state 4 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.380: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.381: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.381: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.381: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.382: Device reported finger status change: FP_FINGER_STATUS_NONE 294s (process:2447): libfprint-device-DEBUG: 05:01:53.382: Device reported enroll progress, reported 8 of 8 have been completed 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.382: [realtek] Enroll entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.382: Device reported finger status change: FP_FINGER_STATUS_NEEDED 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.382: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.382: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.382: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.383: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.383: [realtek] Enroll entering state 3 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.383: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.383: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.384: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.384: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.385: Device reported finger status change: FP_FINGER_STATUS_PRESENT 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.385: [realtek] Enroll entering state 4 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.385: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.385: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.386: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.386: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.387: Device reported finger status change: FP_FINGER_STATUS_NONE 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.387: [realtek] Enroll entering state 5 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.387: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.387: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.387: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.388: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.389: [realtek] Enroll entering state 6 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.389: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.389: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.389: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.390: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.390: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.391: [realtek] Enroll completed successfully 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.391: Enrollment complete! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.391: Device reported enroll completion 294s (process:2447): libfprint-device-DEBUG: 05:01:53.391: Print for finger FP_FINGER_UNKNOWN enrolled 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.391: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-device-DEBUG: 05:01:53.391: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.391: Not updating temperature model, device can run continuously! 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.391: 71309713: ../libfprint/drivers/realtek/realtek.c:1344 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.391: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.392: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.392: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.393: Query templates complete! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.393: Device reported listing completion 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.393: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-device-DEBUG: 05:01:53.393: Completing action FPI_DEVICE_ACTION_LIST in idle! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.393: Not updating temperature model, device can run continuously! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.394: Not updating temperature model, device can run continuously! 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.394: 71312515: ../libfprint/drivers/realtek/realtek.c:1177 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.394: [realtek] Verify & Identify entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.394: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.394: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.395: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.396: [realtek] Verify & Identify entering state 1 294s (process:2447): libfprint-device-DEBUG: 05:01:53.396: Device reported finger status change: FP_FINGER_STATUS_NEEDED 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.396: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.396: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.396: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.396: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.397: [realtek] Verify & Identify entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.397: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.397: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.397: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.398: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.399: Device reported finger status change: FP_FINGER_STATUS_PRESENT 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.399: [realtek] Verify & Identify entering state 3 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.399: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.399: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.399: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.400: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.400: Device reported finger status change: FP_FINGER_STATUS_NONE 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.400: [realtek] Verify & Identify entering state 4 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.400: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.400: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.401: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.401: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.402: Device reported verify result 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.402: [realtek] Verify & Identify entering state 5 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.402: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.402: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.402: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.402: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.403: [realtek] Verify & Identify completed successfully 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.403: Verify complete! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.403: Device reported verify completion 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.403: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-device-DEBUG: 05:01:53.403: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.403: Not updating temperature model, device can run continuously! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.404: Not updating temperature model, device can run continuously! 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.404: 71322411: ../libfprint/drivers/realtek/realtek.c:1177 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.404: [realtek] Verify & Identify entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.404: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.405: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.405: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.406: [realtek] Verify & Identify entering state 1 294s (process:2447): libfprint-device-DEBUG: 05:01:53.406: Device reported finger status change: FP_FINGER_STATUS_NEEDED 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.406: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.406: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.407: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.407: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.407: [realtek] Verify & Identify entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.407: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.407: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.408: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.408: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.409: Device reported finger status change: FP_FINGER_STATUS_PRESENT 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.409: [realtek] Verify & Identify entering state 3 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.409: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.409: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.409: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.410: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.411: Device reported finger status change: FP_FINGER_STATUS_NONE 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.411: [realtek] Verify & Identify entering state 4 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.411: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.411: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.411: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.412: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-device-DEBUG: 05:01:53.413: Device reported identify result 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.413: [realtek] Verify & Identify completed successfully 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.413: Verify complete! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.413: Device reported identify completion 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.413: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-device-DEBUG: 05:01:53.413: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.413: Not updating temperature model, device can run continuously! 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.413: 71332121: ../libfprint/drivers/realtek/realtek.c:1313 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.414: [realtek] Delete print entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.414: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.414: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.415: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.415: [realtek] Delete print entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.415: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.416: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.416: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.416: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.417: [realtek] Delete print completed successfully 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.417: Delete print complete! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.417: Device reported deletion completion 294s (process:2447): libfprint-SSM-DEBUG: 05:01:53.417: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 294s (process:2447): libfprint-device-DEBUG: 05:01:53.417: Completing action FPI_DEVICE_ACTION_DELETE in idle! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.417: Not updating temperature model, device can run continuously! 294s (process:2447): libfprint-realtek-DEBUG: 05:01:53.417: 71335399: ../libfprint/drivers/realtek/realtek.c:1301 294s (process:2447): libfprint-device-DEBUG: 05:01:53.417: Device reported close completion 294s (process:2447): libfprint-device-DEBUG: 05:01:53.417: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 294s (process:2447): libfprint-device-DEBUG: 05:01:53.417: Not updating temperature model, device can run continuously! 294s enrolling 294s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xebc00f17e100 (FpiDeviceRealtek at 0x911bb80)>, 1, None, None, None) 294s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xebc00f17e100 (FpiDeviceRealtek at 0x911bb80)>, 2, None, None, None) 294s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xebc00f17e100 (FpiDeviceRealtek at 0x911bb80)>, 3, None, None, None) 294s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xebc00f17e100 (FpiDeviceRealtek at 0x911bb80)>, 4, None, None, None) 294s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xebc00f17e100 (FpiDeviceRealtek at 0x911bb80)>, 5, None, None, None) 294s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xebc00f17e100 (FpiDeviceRealtek at 0x911bb80)>, 6, None, None, None) 294s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xebc00f17e100 (FpiDeviceRealtek at 0x911bb80)>, 7, None, None, None) 294s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xebc00f17e100 (FpiDeviceRealtek at 0x911bb80)>, 8, None, None, None) 294s enroll done 294s listing 294s listing done 294s verifying 294s verify done 294s async identifying 294s indentification_done: 294s deleting 294s delete done 294s ** (umockdev-run:2443): DEBUG: 05:01:53.452: umockdev.vala:154: Removing test bed /tmp/umockdev.EX5D22 294s (umockdev-run:2443): GLib-DEBUG: 05:01:53.456: unsetenv() is not thread-safe and should not be used after threads are created 294s PASS: libfprint-2/driver-realtek.test 294s Running test: libfprint-2/driver-aes2501.test 294s ** (umockdev-run:2455): DEBUG: 05:01:53.521: umockdev.vala:127: Created udev test bed /tmp/umockdev.Y09J22 294s ** (umockdev-run:2455): DEBUG: 05:01:53.522: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 294s ** (umockdev-run:2455): DEBUG: 05:01:53.523: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 294s ** (umockdev-run:2455): DEBUG: 05:01:53.525: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Y09J22/dev/bus/usb/001/044 294s ** (umockdev-run:2455): DEBUG: 05:01:53.525: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 294s ** (umockdev-run:2455): DEBUG: 05:01:53.526: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 294s ** (umockdev-run:2455): DEBUG: 05:01:53.528: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Y09J22/dev/bus/usb/001/001 294s ** (umockdev-run:2455): DEBUG: 05:01:53.528: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 294s ** (umockdev-run:2455): DEBUG: 05:01:53.528: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 294s (process:2459): libfprint-context-DEBUG: 05:01:53.645: Initializing FpContext (libfprint version 1.94.9+tod1) 294s (process:2459): libfprint-tod-DEBUG: 05:01:53.645: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 294s (process:2459): libfprint-context-DEBUG: 05:01:53.648: No driver found for USB device 1D6B:0002 294s (process:2459): libfprint-device-DEBUG: 05:01:53.648: Device reported probe completion 294s (process:2459): libfprint-device-DEBUG: 05:01:53.648: Completing action FPI_DEVICE_ACTION_PROBE in idle! 294s (process:2459): libfprint-device-DEBUG: 05:01:53.648: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 294s (process:2459): libfprint-image_device-DEBUG: 05:01:53.650: Image device open completed 294s (process:2459): libfprint-device-DEBUG: 05:01:53.650: Device reported open completion 294s (process:2459): libfprint-device-DEBUG: 05:01:53.650: Completing action FPI_DEVICE_ACTION_OPEN in idle! 294s (process:2459): libfprint-device-DEBUG: 05:01:53.650: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 294s (process:2459): libfprint-device-DEBUG: 05:01:53.650: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 294s (process:2459): libfprint-image_device-DEBUG: 05:01:53.650: Activating image device 294s (process:2459): libfprint-image_device-DEBUG: 05:01:53.650: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 294s (process:2459): libfprint-SSM-DEBUG: 05:01:53.650: [aes2501] ACTIVATE_NUM_STATES entering state 0 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.650: write 38 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.653: all registers written 294s (process:2459): libfprint-SSM-DEBUG: 05:01:53.653: [aes2501] ACTIVATE_NUM_STATES entering state 1 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.653: read data 1 294s (process:2459): libfprint-SSM-DEBUG: 05:01:53.653: [aes2501] ACTIVATE_NUM_STATES entering state 2 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.653: write 7 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.654: all registers written 294s (process:2459): libfprint-SSM-DEBUG: 05:01:53.654: [aes2501] ACTIVATE_NUM_STATES entering state 3 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.654: 71572727: ../libfprint/drivers/aes2501.c:140 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.654: write 1 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.655: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.656: reg 0xaf = 20 294s (process:2459): libfprint-SSM-DEBUG: 05:01:53.656: [aes2501] ACTIVATE_NUM_STATES entering state 5 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.656: write 7 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.656: all registers written 294s (process:2459): libfprint-SSM-DEBUG: 05:01:53.656: [aes2501] ACTIVATE_NUM_STATES entering state 6 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.656: write 16 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.657: all registers written 294s (process:2459): libfprint-SSM-DEBUG: 05:01:53.657: [aes2501] ACTIVATE_NUM_STATES completed successfully 294s (process:2459): libfprint-image_device-DEBUG: 05:01:53.657: Image device activation completed 294s (process:2459): libfprint-image_device-DEBUG: 05:01:53.657: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 294s (process:2459): libfprint-image_device-DEBUG: 05:01:53.657: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 294s (process:2459): libfprint-device-DEBUG: 05:01:53.657: Device reported finger status change: FP_FINGER_STATUS_NEEDED 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.657: 71575618: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.657: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.659: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.660: 71578724: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.660: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.662: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.663: 71581489: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.663: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.665: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.665: 71583879: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.665: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.667: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.668: 71586352: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.668: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.670: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.670: 71589096: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.670: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.672: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.673: 71591633: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.673: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.675: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.675: 71593987: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.675: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.677: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.678: 71596394: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.678: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.679: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.680: 71598650: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.680: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.681: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.682: 71600809: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.682: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.684: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.684: 71603057: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.684: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.686: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.686: 71605074: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.686: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.688: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.688: 71607132: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.688: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.690: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.690: 71609075: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.690: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.692: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.692: 71610981: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.692: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.694: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.694: 71613163: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.695: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.696: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.697: 71615241: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.697: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.698: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.699: 71617191: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.699: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.701: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.701: 71619729: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.701: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.703: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.703: 71621752: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.703: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.705: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.705: 71623768: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.705: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.707: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.707: 71625851: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.707: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.709: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.709: 71627852: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.709: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.711: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.711: 71630114: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.711: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.713: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.714: 71632426: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.714: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.715: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.716: 71634613: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.716: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.718: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.718: 71636813: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.718: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.720: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.720: 71639083: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.720: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.722: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.723: 71641344: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.723: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.724: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.725: 71643671: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.725: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.727: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.727: 71645960: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.727: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.729: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.730: 71648516: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.730: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.731: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.732: 71650651: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.732: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.734: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.734: 71652750: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.734: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.735: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.736: 71654648: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.736: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.738: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.738: 71656864: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.738: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.740: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.740: 71658994: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.740: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.742: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.742: 71661130: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.743: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.744: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.745: 71663215: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.745: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.746: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.747: 71665362: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.747: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.748: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.749: 71667772: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.749: write 23 regs 294s (process:2459): libfprint-device-DEBUG: 05:01:53.750: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.751: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.751: 71669761: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.751: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.753: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.753: 71671963: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.753: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.755: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.755: 71674085: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.755: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.757: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.758: 71676451: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.758: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.760: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.760: 71679159: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.761: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.762: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.763: 71681494: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.763: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.765: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.765: 71683883: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.765: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.767: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.768: 71686463: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.768: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.769: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.770: 71688705: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.770: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.772: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.772: 71690934: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.773: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.774: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.775: 71693508: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.775: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.776: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.777: 71695558: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.777: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.779: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.779: 71697776: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.779: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.781: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.781: 71699948: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.781: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.783: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.784: 71702309: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.784: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.785: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.786: 71704621: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.786: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.788: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.788: 71706920: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.788: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.790: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.791: 71709643: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.791: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.792: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.793: 71711682: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.793: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.795: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.795: 71713932: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.795: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.797: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.797: 71716136: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.798: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.799: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.800: 71718474: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.800: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.801: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.802: 71720633: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.802: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.804: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.804: 71722983: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.804: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.806: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.807: 71725401: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.807: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.808: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.809: 71727731: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.809: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.811: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.811: 71730136: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.811: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.813: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.814: 71732283: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.814: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.815: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.816: 71734669: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.816: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.818: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.818: 71736893: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.818: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.820: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.821: 71739268: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.821: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.822: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.823: 71741362: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.823: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.824: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.825: 71743623: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.825: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.826: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.827: 71745715: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.827: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.829: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.829: 71747774: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.829: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.831: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.831: 71750039: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.831: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.833: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.834: 71752253: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.834: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.835: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.836: 71754300: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.836: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.837: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.838: 71756515: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.838: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.839: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.840: 71758638: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.840: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.841: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.842: 71760792: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.842: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.844: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.844: 71762888: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.844: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.846: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.846: 71765036: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.846: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.848: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.849: 71767319: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.849: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.850: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.851: 71769514: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.851: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.852: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.853: 71771661: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.853: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.854: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.855: 71773819: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.855: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.857: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.857: 71775936: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.857: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.859: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.860: 71778230: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.860: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.861: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.862: 71780387: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.862: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.863: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.864: 71782693: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.864: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.866: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.866: 71785047: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.866: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.868: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.869: 71787307: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.869: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.870: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.871: 71789498: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.871: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.872: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.873: 71791743: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.873: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.875: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.875: 71794124: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.875: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.877: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.878: 71796366: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.878: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.879: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.880: 71798649: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.880: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.882: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.882: 71800784: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.882: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.884: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.884: 71802903: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.884: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.886: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.886: 71805159: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.887: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.892: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.893: 71811763: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.893: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.894: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.895: 71813354: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.895: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.896: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.896: 71815040: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.896: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.898: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.899: 71817419: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.899: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.901: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.902: 71820667: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.902: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.904: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.904: 71823161: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.905: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.906: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.907: 71825482: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.907: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.909: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.909: 71827881: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.909: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.911: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.912: 71830179: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.912: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.913: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.914: 71832723: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.914: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.916: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.916: 71835012: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.916: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.918: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.919: 71837549: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.919: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.921: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.921: 71839824: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.921: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.923: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.923: 71842043: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.923: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.925: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.926: 71844292: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.926: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.927: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.928: 71846579: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.928: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.930: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.930: 71848882: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.930: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.932: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.932: 71851039: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.932: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.934: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.935: 71853242: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.935: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.936: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.937: 71855356: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.937: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.938: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.939: 71857349: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.939: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.940: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.941: 71859964: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.941: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.943: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.944: 71862233: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.944: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.945: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.946: 71864622: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.946: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.948: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.948: 71866867: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.948: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.950: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.950: 71868962: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.950: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.952: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.953: 71871402: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.953: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.954: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.955: 71873442: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.955: write 23 regs 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.956: all registers written 294s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.957: 71875634: ../libfprint/drivers/aes2501.c:310 294s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.957: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.959: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.959: 71878029: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.959: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.961: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.962: 71880402: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.962: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.963: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.964: 71882722: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.964: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.966: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.967: 71885202: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.967: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.968: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.969: 71887572: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.969: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.971: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.971: 71890045: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.971: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.973: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.974: 71892658: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.974: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.976: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.976: 71895030: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.976: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.978: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.979: 71897301: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.979: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.980: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.981: 71899500: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.981: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.982: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.983: 71901615: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.983: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.984: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.985: 71903734: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.985: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.987: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.987: 71905858: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.987: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.989: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.989: 71908164: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.990: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.991: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.992: 71910352: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.992: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.993: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.994: 71912577: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.994: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.995: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.996: 71914665: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.996: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.998: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:53.998: 71916983: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:53.998: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.000: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.000: 71919019: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.000: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.002: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.002: 71921118: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.002: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.004: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.005: 71923296: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.005: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.006: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.007: 71925497: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.007: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.008: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.009: 71927471: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.009: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.010: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.011: 71929537: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.011: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.012: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.013: 71931554: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.013: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.015: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.015: 71933744: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.015: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.017: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.017: 71935811: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.017: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.019: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.020: 71938228: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.020: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.021: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.022: 71940294: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.022: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.023: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.024: 71942305: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.024: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.025: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.026: 71944435: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.026: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.027: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.028: 71946488: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.028: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.029: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.030: 71948664: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.030: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.032: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.032: 71950791: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.032: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.034: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.034: 71952939: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.034: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.036: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.036: 71955025: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.036: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.038: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.039: 71957193: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.039: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.040: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.041: 71959306: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.041: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.042: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.043: 71961398: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.043: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.044: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.045: 71963590: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.045: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.046: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.047: 71965611: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.047: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.049: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.049: 71967779: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.049: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.051: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.051: 71969816: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.051: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.053: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.053: 71971808: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.053: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.055: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.055: 71973877: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.055: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.057: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.057: 71975997: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.057: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.059: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.059: 71977995: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.059: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.061: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.061: 71980034: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.061: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.063: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.063: 71981899: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.063: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.065: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.065: 71983933: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.065: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.067: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.067: 71985871: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.067: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.069: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.069: 71987909: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.069: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.071: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.071: 71989843: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.071: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.073: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.073: 71991862: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.073: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.075: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.075: 71993909: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.075: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.077: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.077: 71995967: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.077: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.079: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.079: 71998115: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.079: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.081: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.081: 71999987: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.081: write 23 regs 295s Executing: libfprint-2/driver-aes2501.test 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.084: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.084: 72002902: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.084: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.086: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.086: 72004844: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.086: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.088: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.088: 72006897: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.088: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.090: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.090: 72009082: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.090: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.092: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.092: 72011079: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.092: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.094: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.095: 72013206: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.095: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.096: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.097: 72015271: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.097: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.098: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.099: 72017297: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.099: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.100: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.101: 72019381: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.101: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.102: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.103: 72021384: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.103: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.104: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.105: 72023409: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.105: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.106: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.107: 72025399: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.107: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.108: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.109: 72027448: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.109: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.110: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.111: 72029435: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.111: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.112: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.113: 72031501: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.113: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.114: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.115: 72033590: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.115: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.116: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.117: 72035614: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.117: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.118: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.119: 72037537: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.119: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.120: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.121: 72039674: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.121: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.123: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.123: 72041984: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.123: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.125: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.125: 72043984: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.125: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.127: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.127: 72045986: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.127: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.129: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.129: 72048023: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.129: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.131: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.131: 72050018: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.131: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.133: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.133: 72051986: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.133: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.135: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.135: 72053910: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.135: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.137: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.137: 72056037: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.137: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.139: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.139: 72057948: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.139: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.141: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.141: 72059981: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.141: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.143: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.143: 72061953: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.143: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.145: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.145: 72063865: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.145: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.147: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.147: 72065996: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.147: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.149: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.149: 72067975: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.149: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.151: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.151: 72069970: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.151: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.153: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.154: 72072189: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.154: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.155: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.156: 72074334: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.156: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.157: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.158: 72076308: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.158: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.159: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.160: 72078284: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.160: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.161: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.162: 72080388: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.162: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.163: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.164: 72082492: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.164: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.165: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.166: 72084466: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.166: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.167: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.168: 72086441: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.168: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.169: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.170: 72088442: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.170: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.171: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.172: 72090480: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.172: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.173: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.174: 72092417: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.174: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.175: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.176: 72094563: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.176: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.177: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.178: 72096542: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.178: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.180: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.180: 72098682: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.180: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.181: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.182: 72100789: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.182: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.184: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.184: 72102839: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.184: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.186: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.186: 72104893: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.186: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.188: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.188: 72107033: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.188: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.190: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.190: 72109164: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.191: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.192: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.194: 72112209: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.194: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.195: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.196: 72114559: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.196: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.197: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.198: 72116530: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.198: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.199: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.200: 72118618: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.200: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.202: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.202: 72120854: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.202: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.204: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.204: 72122968: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.204: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.206: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.206: 72124963: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.206: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.208: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.208: 72127048: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.208: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.210: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.211: 72129212: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.211: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.212: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.213: 72131351: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.213: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.214: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.215: 72133800: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.215: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.217: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.217: 72135809: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.217: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.219: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.219: 72137860: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.219: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.221: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.222: 72140273: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.222: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.223: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.224: 72142489: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.224: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.225: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.226: 72144501: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.226: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.227: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.228: 72146500: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.228: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.229: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.230: 72148536: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.230: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.232: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.232: 72150751: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.232: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.234: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.234: 72152950: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.234: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.236: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.236: 72154943: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.236: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.238: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.238: 72156938: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.238: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.240: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.240: 72159065: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.240: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.242: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.242: 72161031: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.242: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.244: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.244: 72163063: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.244: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.246: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.246: 72165130: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.246: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.248: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.249: 72167209: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.249: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.250: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.251: 72169299: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.251: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.252: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.253: 72171234: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.253: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.254: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.255: 72173181: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.255: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.256: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.257: 72175229: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.257: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.258: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.259: 72177328: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.259: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.260: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.261: 72179446: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.261: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.262: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.263: 72181549: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.263: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.264: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.265: 72183634: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.265: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.266: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.267: 72185605: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.267: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.268: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.269: 72187849: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.269: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.271: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.271: 72189978: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.271: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.273: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.273: 72192158: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.274: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.275: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.276: 72194201: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.276: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.277: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.277: 72196165: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.278: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.279: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.280: 72198289: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.280: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.281: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.282: 72200384: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.282: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.283: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.284: 72202480: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.284: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.285: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.286: 72204467: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.286: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.287: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.288: 72206524: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.288: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.289: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.290: 72208421: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.290: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.291: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.292: 72210344: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.292: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.293: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.294: 72212291: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.294: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.295: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.296: 72214302: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.296: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.297: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.298: 72216378: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.298: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.299: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.300: 72218291: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.300: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.301: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.302: 72220303: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.302: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.303: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.304: 72222340: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.304: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.305: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.306: 72224412: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.306: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.307: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.308: 72226457: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.308: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.309: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.310: 72228486: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.310: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.311: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.312: 72230538: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.312: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.314: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.314: 72232754: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.314: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.316: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.316: 72234804: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.316: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.318: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.318: 72236952: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.318: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.320: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.321: 72239264: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.321: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.322: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.323: 72241581: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.323: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.325: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.325: 72243803: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.325: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.327: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.327: 72246024: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.327: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.329: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.330: 72248759: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.330: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.332: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.332: 72251146: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.332: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.334: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.335: 72253277: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.335: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.336: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.337: 72255353: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.337: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.338: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.339: 72257350: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.339: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.340: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.341: 72259411: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.341: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.342: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.343: 72261555: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.343: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.344: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.345: 72263643: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.345: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.347: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.347: 72265890: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.347: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.349: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.349: 72268029: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.349: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.351: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.351: 72270139: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.351: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.353: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.354: 72272278: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.354: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.355: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.356: 72274472: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.356: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.357: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.358: 72276664: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.358: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.360: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.360: 72278858: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.360: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.362: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.362: 72281056: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.362: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.364: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.364: 72283111: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.364: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.366: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.367: 72285220: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.367: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.368: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.369: 72287364: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.369: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.370: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.371: 72289271: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.371: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.372: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.373: 72291301: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.373: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.374: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.375: 72293300: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.375: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.376: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.377: 72295337: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.377: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.378: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.379: 72297344: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.379: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.380: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.381: 72299396: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.381: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.382: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.383: 72301358: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.383: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.384: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.385: 72303359: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.385: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.386: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.387: 72305386: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.387: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.388: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.389: 72307442: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.389: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.390: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.391: 72309430: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.391: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.392: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.393: 72311401: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.393: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.394: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.395: 72313473: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.395: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.396: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.397: 72315349: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.397: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.398: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.399: 72317395: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.399: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.400: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.401: 72319558: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.401: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.402: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.403: 72321675: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.403: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.404: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.405: 72323575: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.405: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.406: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.407: 72325583: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.407: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.408: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.409: 72327537: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.409: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.410: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.411: 72329498: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.411: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.412: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.413: 72331604: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.413: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.414: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.415: 72333493: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.415: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.416: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.417: 72335476: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.417: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.418: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.419: 72337523: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.419: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.420: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.421: 72339592: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.421: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.422: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.423: 72341622: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.423: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.424: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.425: 72343748: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.425: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.427: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.427: 72345843: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.427: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.429: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.429: 72347741: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.429: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.431: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.431: 72349733: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.431: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.432: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.433: 72351606: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.433: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.434: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.435: 72353538: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.435: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.436: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.437: 72355610: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.437: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.439: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.439: 72358024: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.439: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.441: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.441: 72359993: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.441: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.443: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.443: 72361927: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.443: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.445: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.445: 72363981: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.445: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.447: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.447: 72366014: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.447: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.449: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.449: 72368165: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.450: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.451: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.452: 72370327: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.452: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.453: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.454: 72372202: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.454: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.455: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.456: 72374187: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.456: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.457: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.458: 72376185: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.458: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.459: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.460: 72378197: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.460: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.461: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.462: 72380184: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.462: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.463: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.464: 72382238: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.464: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.465: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.466: 72384178: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.466: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.467: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.468: 72386543: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.468: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.469: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.470: 72388728: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.470: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.472: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.472: 72390990: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.472: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.474: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.474: 72393069: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.474: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.476: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.477: 72395515: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.477: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.479: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.479: 72397822: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.479: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.481: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.481: 72400135: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.481: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.483: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.484: 72402238: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.484: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.485: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.486: 72404454: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.486: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.487: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.488: 72406672: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.488: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.490: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.490: 72409025: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.490: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.492: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.493: 72411229: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.493: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.495: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.495: 72413850: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.495: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.497: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.498: 72416505: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.498: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.500: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.500: 72419074: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.500: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.502: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.503: 72421448: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.503: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.504: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.505: 72423589: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.505: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.507: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.507: 72425797: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.507: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.509: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.509: 72428029: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.509: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.511: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.512: 72430423: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.512: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.513: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.514: 72432558: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.514: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.515: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.516: 72434706: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.516: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.518: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.518: 72436990: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.518: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.520: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.520: 72439153: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.521: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.522: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.523: 72441366: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.523: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.524: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.525: 72443679: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.525: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.527: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.527: 72445782: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.527: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.529: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.529: 72448033: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.529: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.531: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.531: 72450145: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.531: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.533: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.534: 72452294: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.534: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.535: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.536: 72454467: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.536: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.537: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.538: 72456636: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.538: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.540: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.540: 72458750: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.540: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.542: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.542: 72461021: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.542: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.544: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.545: 72463189: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.545: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.546: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.547: 72465429: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.547: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.548: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.549: 72467558: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.549: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.551: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.551: 72469783: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.551: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.553: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.553: 72471998: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.553: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.555: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.555: 72474138: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.555: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.557: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.558: 72476317: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.558: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.559: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.560: 72478472: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.560: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.561: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.562: 72480483: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.562: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.563: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.564: 72482566: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.564: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.565: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.566: 72484695: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.566: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.568: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.568: 72486801: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.568: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.570: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.570: 72489057: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.570: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.572: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.572: 72491067: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.572: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.574: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.575: 72493276: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.575: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.576: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.577: 72495734: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.577: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.579: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.579: 72498052: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.579: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.581: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.582: 72500188: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.582: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.583: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.584: 72502281: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.584: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.585: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.586: 72504418: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.586: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.587: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.588: 72506425: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.588: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.589: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.590: 72508554: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.590: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.591: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.592: 72510627: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.592: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.594: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.594: 72513096: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.594: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.596: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.596: 72515037: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.596: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.598: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.598: 72516888: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.598: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.600: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.600: 72519065: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.600: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.602: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.603: 72521210: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.603: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.604: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.605: 72523376: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.605: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.606: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.607: 72525319: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.607: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.608: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.609: 72527311: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.609: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.610: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.611: 72529301: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.611: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.612: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.613: 72531429: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.613: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.614: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.615: 72533503: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.615: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.616: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.617: 72535455: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.617: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.618: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.619: 72537534: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.619: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.620: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.621: 72539563: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.621: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.622: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.623: 72541670: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.623: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.625: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.625: 72543826: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.625: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.627: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.627: 72546115: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.627: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.629: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.630: 72548341: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.630: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.631: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.632: 72550590: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.632: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.634: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.634: 72552812: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.634: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.636: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.636: 72555035: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.636: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.638: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.638: 72557150: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.639: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.640: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.641: 72559246: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.641: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.642: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.643: 72561384: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.643: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.644: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.645: 72563517: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.645: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.646: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.647: 72565744: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.647: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.649: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.649: 72568045: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.649: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.651: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.652: 72570182: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.652: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.653: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.654: 72572310: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.654: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.655: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.656: 72574768: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.656: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.658: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.658: 72577025: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.658: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.660: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.661: 72579317: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.661: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.662: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.663: 72581629: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.663: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.664: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.665: 72583802: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.665: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.667: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.667: 72585955: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.667: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.669: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.670: 72588403: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.670: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.671: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.672: 72590729: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.672: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.674: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.674: 72593035: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.674: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.676: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.677: 72595430: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.677: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.678: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.679: 72597594: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.679: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.681: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.681: 72599755: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.681: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.683: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.683: 72601883: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.683: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.685: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.685: 72604057: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.685: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.687: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.688: 72606221: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.688: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.689: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.690: 72608334: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.690: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.692: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.692: 72610719: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.692: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.694: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.694: 72612721: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.694: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.695: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.696: 72614683: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.696: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.697: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.698: 72616748: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.698: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.700: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.700: 72618717: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.700: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.701: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.702: 72620778: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.702: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.704: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.704: 72622876: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.704: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.706: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.706: 72625133: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.706: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.708: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.709: 72627371: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.709: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.710: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.711: 72629565: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.711: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.713: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.713: 72631852: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.713: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.715: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.716: 72634185: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.716: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.717: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.718: 72636503: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.718: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.719: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.720: 72638717: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.720: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.722: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.722: 72640826: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.722: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.724: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.724: 72642939: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.724: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.726: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.727: 72645158: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.727: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.728: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.729: 72647416: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.729: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.730: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.731: 72649483: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.731: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.732: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.733: 72651566: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.733: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.734: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.735: 72653659: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.735: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.737: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.737: 72655932: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.737: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.739: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.740: 72658322: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.740: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.742: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.742: 72660866: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.742: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.744: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.744: 72663021: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.744: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.746: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.746: 72665049: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.746: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.748: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.748: 72666980: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.748: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.750: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.750: 72669076: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.750: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.752: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.753: 72671238: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.753: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.754: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.755: 72673297: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.755: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.756: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.757: 72675403: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.757: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.758: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.759: 72677472: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.759: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.760: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.761: 72679723: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.761: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.763: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.763: 72682142: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.764: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.765: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.766: 72684445: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.766: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.767: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.768: 72686582: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.768: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.770: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.770: 72688889: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.770: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.772: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.772: 72691015: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.772: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.774: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.775: 72693250: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.775: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.776: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.777: 72695579: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.777: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.779: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.779: 72698015: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.779: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.781: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.781: 72700129: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.782: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.783: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.784: 72702265: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.784: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.785: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.786: 72704417: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.786: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.787: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.788: 72706558: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.788: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.789: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.790: 72708648: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.790: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.792: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.792: 72710864: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.792: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.794: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.795: 72713190: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.795: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.796: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.797: 72715478: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.797: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.798: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.799: 72717651: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.799: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.801: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.801: 72719926: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.801: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.803: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.803: 72722149: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.804: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.805: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.806: 72724419: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.806: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.807: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.808: 72726447: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.808: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.809: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.810: 72728683: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.810: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.812: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.812: 72730886: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.812: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.814: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.814: 72733031: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.814: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.816: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.817: 72735275: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.817: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.818: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.819: 72737319: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.819: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.820: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.821: 72739517: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.821: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.822: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.823: 72741639: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.823: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.824: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.825: 72743882: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.825: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.827: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.827: 72746107: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.827: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.829: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.830: 72748419: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.830: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.831: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.832: 72750654: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.832: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.834: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.834: 72752929: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.834: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.836: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.837: 72755260: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.837: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.838: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.839: 72757299: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.839: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.840: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.841: 72759306: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.841: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.842: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.843: 72761219: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.843: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.844: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.844: 72763041: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.844: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.846: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.846: 72765020: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.846: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.848: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.849: 72767246: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.849: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.850: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.851: 72769558: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.851: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.852: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.853: 72771745: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.853: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.855: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.855: 72773999: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.855: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.857: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.858: 72776187: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.858: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.859: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.860: 72778330: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.860: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.861: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.862: 72780757: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.862: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.864: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.864: 72782969: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.864: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.866: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.867: 72785284: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.867: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.868: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.869: 72787444: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.869: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.870: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.871: 72789784: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.871: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.873: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.874: 72792216: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.874: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.875: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.876: 72794501: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.876: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.878: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.879: 72797251: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.879: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.880: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.881: 72799391: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.881: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.882: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.883: 72801617: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.883: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.885: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.885: 72803915: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.885: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.887: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.887: 72806142: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.888: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.889: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.890: 72808351: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.890: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.891: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.892: 72810487: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.892: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.893: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.894: 72812707: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.894: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.896: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.896: 72814931: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.896: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.898: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.898: 72816966: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.898: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.900: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.900: 72818878: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.900: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.902: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.902: 72820954: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.902: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.904: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.904: 72822877: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.904: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.906: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.906: 72824822: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.906: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.908: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.908: 72826723: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.908: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.909: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.910: 72828580: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.910: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.911: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.912: 72830687: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.912: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.913: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.914: 72832571: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.914: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.915: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.916: 72834363: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.916: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.917: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.918: 72836319: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.918: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.919: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.920: 72838470: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.920: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.921: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.922: 72840293: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.922: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.923: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.923: 72842131: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.923: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.925: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.925: 72843941: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.925: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.927: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.927: 72845758: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.927: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.928: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.929: 72847527: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.929: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.930: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.931: 72849256: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.931: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.932: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.932: 72850982: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.932: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.934: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.934: 72852723: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.934: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.935: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.936: 72854518: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.936: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.937: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.938: 72856355: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.938: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.939: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.940: 72858226: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.940: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.941: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.942: 72860286: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.942: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.943: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.943: 72862038: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.943: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.945: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.945: 72863771: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.945: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.947: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.947: 72865725: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.947: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.948: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.949: 72867652: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.949: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.950: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.951: 72869489: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.951: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.952: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.953: 72871566: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.953: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.954: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.955: 72873421: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.955: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.956: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.957: 72875652: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.957: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.958: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.959: 72877558: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.959: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.960: all registers written 295s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.961: 72879367: ../libfprint/drivers/aes2501.c:310 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.961: write 23 regs 295s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.962: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.963: 72881399: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.963: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.964: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.965: 72883325: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.965: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.966: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.966: 72885168: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.967: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.968: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.968: 72887120: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.968: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.970: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.970: 72888872: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.970: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.972: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.972: 72890720: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.972: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.973: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.974: 72892517: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.974: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.975: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.976: 72894468: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.976: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.977: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.978: 72896354: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.978: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.979: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.980: 72898313: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.980: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.981: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.981: 72900122: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.981: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.983: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.983: 72901830: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.983: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.984: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.985: 72903731: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.985: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.986: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.987: 72905621: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.987: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.988: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.989: 72907568: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.989: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.990: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.991: 72909463: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.991: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.992: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.993: 72911466: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.993: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.994: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.995: 72913475: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.995: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.997: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:54.998: 72916704: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:54.998: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.000: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.001: 72919615: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.001: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.003: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.004: 72922521: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.004: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.006: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.007: 72925551: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.007: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.008: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.009: 72927537: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.009: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.011: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.011: 72929836: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.011: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.013: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.013: 72932130: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.013: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.015: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.016: 72934313: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.016: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.017: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.018: 72936419: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.018: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.019: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.020: 72938534: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.020: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.021: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.022: 72940573: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.022: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.023: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.024: 72942576: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.024: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.025: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.026: 72944610: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.026: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.027: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.028: 72946720: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.028: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.030: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.030: 72948751: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.030: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.032: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.032: 72950985: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.032: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.034: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.034: 72953168: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.035: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.036: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.036: 72955156: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.037: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.038: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.038: 72957032: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.038: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.040: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.041: 72959269: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.041: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.042: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.043: 72961320: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.043: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.045: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.045: 72963921: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.045: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.047: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.047: 72965950: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.047: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.049: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.049: 72968058: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.049: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.051: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.052: 72970292: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.052: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.053: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.054: 72972427: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.054: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.055: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.056: 72974469: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.056: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.057: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.058: 72976610: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.058: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.059: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.060: 72978667: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.060: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.061: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.062: 72980667: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.062: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.063: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.064: 72982633: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.064: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.065: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.066: 72984706: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.066: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.067: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.068: 72986726: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.068: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.070: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.070: 72988759: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.070: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.072: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.072: 72990890: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.072: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.074: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.074: 72992960: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.074: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.076: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.076: 72995023: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.076: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.078: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.078: 72997023: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.078: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.080: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.080: 72999146: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.081: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.082: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.083: 73001379: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.083: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.084: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.085: 73003443: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.085: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.086: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.087: 73005456: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.087: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.088: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.089: 73007421: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.089: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.090: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.091: 73009360: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.091: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.092: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.093: 73011241: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.093: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.094: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.095: 73013224: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.095: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.096: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.097: 73015297: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.097: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.098: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.099: 73017280: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.099: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.100: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.101: 73019497: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.101: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.102: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.103: 73021409: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.103: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.104: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.105: 73023316: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.105: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.106: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.106: 73025154: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.107: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.108: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.109: 73027339: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.109: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.110: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.111: 73029544: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.111: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.112: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.113: 73031602: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.113: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.115: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.115: 73033860: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.115: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.117: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.118: 73036314: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.118: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.119: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.120: 73038629: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.120: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.122: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.122: 73040800: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.122: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.124: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.124: 73042805: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.124: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.125: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.126: 73044690: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.126: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.127: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.128: 73046553: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.128: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.129: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.130: 73048788: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.130: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.132: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.132: 73050815: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.132: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.134: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.134: 73052785: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.134: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.136: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.136: 73054791: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.136: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.138: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.138: 73056680: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.138: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.139: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.140: 73058566: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.140: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.141: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.142: 73060422: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.142: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.143: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.144: 73062385: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.144: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.145: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.146: 73064338: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.146: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.147: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.148: 73066286: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.148: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.149: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.150: 73068368: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.150: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.151: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.152: 73070383: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.152: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.153: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.154: 73072319: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.154: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.155: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.156: 73074289: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.156: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.157: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.158: 73076257: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.158: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.159: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.160: 73078215: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.160: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.161: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.162: 73080315: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.162: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.163: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.164: 73082306: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.164: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.165: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.166: 73084311: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.166: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.167: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.168: 73086294: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.168: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.169: all registers written 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.170: 73088348: ../libfprint/drivers/aes2501.c:310 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.170: write 23 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.171: all registers written 296s (process:2459): libfprint-device-DEBUG: 05:01:55.172: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 296s (process:2459): libfprint-image_device-DEBUG: 05:01:55.172: Image device reported finger status: on 296s (process:2459): libfprint-image_device-DEBUG: 05:01:55.172: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.172: 73090607: ../libfprint/drivers/aes2501.c:581 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.172: [aes2501] CAPTURE_NUM_STATES entering state 0 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.172: write 26 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.173: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.173: [aes2501] CAPTURE_NUM_STATES entering state 1 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.174: [aes2501] CAPTURE_NUM_STATES entering state 2 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.174: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.174: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.175: [aes2501] CAPTURE_NUM_STATES entering state 3 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.175: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.175: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.176: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.176: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.176: sum=5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.176: ADREFHI is 50 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.176: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.176: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.177: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.177: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.177: sum=8 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.178: ADREFHI is 48 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.178: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.178: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.178: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.178: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.179: sum=19 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.179: ADREFHI is 40 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.179: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.179: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.179: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.179: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.180: sum=60 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.180: ADREFHI is 38 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.180: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.180: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.180: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.180: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.181: sum=123 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.181: ADREFHI is 30 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.181: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.181: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.181: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.181: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.182: sum=226 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.182: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.182: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.182: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.183: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.183: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.183: sum=461 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.183: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.183: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.183: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.184: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.184: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.184: sum=466 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.184: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.184: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.184: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.185: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.185: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.186: sum=465 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.186: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.186: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.186: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.186: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.186: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.187: sum=620 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.187: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.187: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.187: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.187: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.187: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.188: sum=629 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.188: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.188: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.188: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.188: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.189: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.189: sum=615 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.189: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.189: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.189: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.190: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.190: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.190: sum=585 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.190: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.190: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.190: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.191: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.191: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.191: sum=581 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.192: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.192: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.192: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.192: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.192: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.193: sum=418 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.193: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.193: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.193: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.193: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.193: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.194: sum=406 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.194: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.194: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.194: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.194: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.194: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.195: sum=389 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.195: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.195: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.195: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.196: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.196: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.196: sum=388 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.196: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.196: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.196: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.197: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.197: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.197: sum=393 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.197: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.197: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.197: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.198: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.198: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.198: sum=389 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.198: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.199: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.199: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.199: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.199: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.200: sum=379 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.200: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.200: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.200: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.200: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.200: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.201: sum=361 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.201: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.201: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.201: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.201: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.201: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.202: sum=356 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.202: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.202: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.202: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.202: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.203: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.203: sum=193 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.203: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.203: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.203: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.204: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.204: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.204: sum=178 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.204: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.204: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.204: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.205: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.205: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.205: sum=164 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.205: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.205: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.205: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.206: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.206: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.207: sum=157 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.207: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.207: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.207: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.207: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.207: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.208: sum=152 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.208: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.208: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.208: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.208: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.208: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.209: sum=154 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.209: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.209: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.209: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.209: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.209: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.210: sum=157 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.210: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.210: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.210: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.210: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.210: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.211: sum=161 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.211: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.211: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.211: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.211: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.211: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.212: sum=161 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.212: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.212: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.212: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.213: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.213: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.213: sum=161 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.213: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.213: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.213: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.214: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.214: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.214: sum=162 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.214: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.214: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.214: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.215: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.215: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.215: sum=166 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.215: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.215: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.216: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.216: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.216: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.217: sum=143 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.217: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.217: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.217: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.217: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.217: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.218: sum=106 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.218: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.218: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.218: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.218: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.218: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.219: sum=74 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.219: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.219: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.219: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.219: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.219: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.220: sum=51 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.220: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.220: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.220: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.221: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.221: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.221: sum=40 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.221: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.221: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.221: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.222: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.222: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.222: sum=39 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.222: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.222: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.222: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.223: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.223: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.223: sum=19 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.223: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.223: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.223: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.224: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.224: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.225: sum=13 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.225: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.225: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.225: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.225: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.225: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.226: sum=5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.226: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.226: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.226: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.226: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.226: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.227: sum=2 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.227: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.227: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.227: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.227: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.227: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.228: sum=0 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.228: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.228: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.228: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.228: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.228: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.229: sum=0 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.229: ADREFHI is 28 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.229: [aes2501] CAPTURE_NUM_STATES entering state 4 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.229: write 7 regs 296s (process:2459): libfprint-aeslib-DEBUG: 05:01:55.230: all registers written 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.230: [aes2501] CAPTURE_NUM_STATES entering state 5 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.230: sum=0 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.230: ADREFHI is 28 296s (process:2459): libfprint-assembling-DEBUG: 05:01:55.343: calc delta completed in 0.112425 secs 296s (process:2459): libfprint-assembling-DEBUG: 05:01:55.451: calc delta completed in 0.108120 secs 296s (process:2459): libfprint-assembling-DEBUG: 05:01:55.451: errors: 53228 rev: 72653 296s (process:2459): libfprint-assembling-DEBUG: 05:01:55.558: calc delta completed in 0.107579 secs 296s (process:2459): libfprint-assembling-DEBUG: 05:01:55.558: height is 102 296s (process:2459): libfprint-image_device-DEBUG: 05:01:55.559: Image device captured an image 296s (process:2459): libfprint-image_device-DEBUG: 05:01:55.559: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 296s (process:2459): libfprint-device-DEBUG: 05:01:55.559: Device reported finger status change: FP_FINGER_STATUS_PRESENT 296s (process:2459): libfprint-device-DEBUG: 05:01:55.560: Device reported finger status change: FP_FINGER_STATUS_NONE 296s (process:2459): libfprint-image_device-DEBUG: 05:01:55.560: Image device reported finger status: off 296s (process:2459): libfprint-image_device-DEBUG: 05:01:55.560: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 296s (process:2459): libfprint-image_device-DEBUG: 05:01:55.560: Deactivating image device 296s (process:2459): libfprint-image_device-DEBUG: 05:01:55.560: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 296s (process:2459): libfprint-SSM-DEBUG: 05:01:55.560: [aes2501] CAPTURE_NUM_STATES completed successfully 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.560: 73478204: ../libfprint/drivers/aes2501.c:547 296s (process:2459): libfprint-aes2501-DEBUG: 05:01:55.560: 73478208: ../libfprint/drivers/aes2501.c:820 296s (process:2459): libfprint-image_device-DEBUG: 05:01:55.560: Image device deactivation completed 296s (process:2459): libfprint-image_device-DEBUG: 05:01:55.560: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 296s (process:2459): libfprint-image-DEBUG: 05:01:55.565: Minutiae scan completed in 0.004713 secs 296s (process:2459): libfprint-device-DEBUG: 05:01:55.565: Device reported capture completion 296s (process:2459): libfprint-device-DEBUG: 05:01:55.565: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 296s (process:2459): libfprint-device-DEBUG: 05:01:55.565: Updated temperature model after 1.81 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 296s (process:2459): libfprint-image_device-DEBUG: 05:01:55.565: Image device close completed 296s (process:2459): libfprint-device-DEBUG: 05:01:55.565: Device reported close completion 296s (process:2459): libfprint-device-DEBUG: 05:01:55.566: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 296s (process:2459): libfprint-device-DEBUG: 05:01:55.566: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 296s ** (umockdev-run:2455): DEBUG: 05:01:55.639: umockdev.vala:154: Removing test bed /tmp/umockdev.Y09J22 296s (umockdev-run:2455): GLib-DEBUG: 05:01:55.643: unsetenv() is not thread-safe and should not be used after threads are created 296s Comparing PNGs /tmp/libfprint-umockdev-test-48vzpaj3/capture.png and /usr/share/installed-tests/libfprint-2/aes2501/capture.png 296s PASS: libfprint-2/driver-aes2501.test 296s Running test: libfprint-2/virtual-device.test 296s (process:2466): libfprint-context-DEBUG: 05:01:55.808: Initializing FpContext (libfprint version 1.94.9+tod1) 296s (process:2466): libfprint-tod-DEBUG: 05:01:55.808: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 296s (process:2466): libfprint-context-DEBUG: 05:01:55.811: No driver found for USB device 1D6B:0003 296s (process:2466): libfprint-context-DEBUG: 05:01:55.811: No driver found for USB device 0627:0001 296s (process:2466): libfprint-context-DEBUG: 05:01:55.811: No driver found for USB device 1D6B:0002 296s (process:2466): libfprint-context-DEBUG: 05:01:55.811: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-r77j20wx/virtual-device.socket 296s (process:2466): libfprint-context-DEBUG: 05:01:55.811: created 296s (process:2466): libfprint-device-DEBUG: 05:01:55.812: Device reported probe completion 296s (process:2466): libfprint-device-DEBUG: 05:01:55.812: Completing action FPI_DEVICE_ACTION_PROBE in idle! 296s (process:2466): libfprint-device-DEBUG: 05:01:55.812: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 296s test_capture_unsupported (__main__.VirtualDevice.test_capture_unsupported) ... (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.813: 73731182: ../libfprint/drivers/virtual-device.c:387 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.813: 73731264: ../libfprint/drivers/virtual-device-listener.c:153 296s (process:2466): libfprint-device-DEBUG: 05:01:55.813: Device reported open completion 296s (process:2466): libfprint-device-DEBUG: 05:01:55.813: Completing action FPI_DEVICE_ACTION_OPEN in idle! 296s (process:2466): libfprint-device-DEBUG: 05:01:55.813: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.814: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.814: Got instructions of length 16 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.814: Received command SET_KEEP_ALIVE 0 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.814: Keep alive toggled: 0 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.814: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.815: Got instructions of length 19 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.815: Received command SET_ENROLL_STAGES 5 296s (process:2466): libfprint-device-DEBUG: 05:01:55.815: Device reported close completion 296s (process:2466): libfprint-device-DEBUG: 05:01:55.815: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 296s (process:2466): libfprint-device-DEBUG: 05:01:55.815: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 296s ok 296s test_change_enroll_stages (__main__.VirtualDevice.test_change_enroll_stages) ... (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.815: 73733843: ../libfprint/drivers/virtual-device.c:387 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.815: 73733891: ../libfprint/drivers/virtual-device-listener.c:153 296s (process:2466): libfprint-device-DEBUG: 05:01:55.815: Device reported open completion 296s (process:2466): libfprint-device-DEBUG: 05:01:55.815: Completing action FPI_DEVICE_ACTION_OPEN in idle! 296s (process:2466): libfprint-device-DEBUG: 05:01:55.815: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.816: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.816: Got instructions of length 20 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.816: Received command SET_ENROLL_STAGES 20 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.816: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.816: Got instructions of length 19 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.816: Received command SET_ENROLL_STAGES 1 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.817: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.817: Got instructions of length 19 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.817: Received command SET_ENROLL_STAGES 0 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.822: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.822: Got instructions of length 16 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.822: Received command SET_KEEP_ALIVE 0 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.822: Keep alive toggled: 0 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.822: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.822: Got instructions of length 19 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.823: Received command SET_ENROLL_STAGES 5 296s (process:2466): libfprint-device-DEBUG: 05:01:55.823: Device reported close completion 296s (process:2466): libfprint-device-DEBUG: 05:01:55.823: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 296s (process:2466): libfprint-device-DEBUG: 05:01:55.823: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 296s ok 296s test_change_scan_type (__main__.VirtualDevice.test_change_scan_type) ... (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.823: 73741718: ../libfprint/drivers/virtual-device.c:387 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.823: 73741766: ../libfprint/drivers/virtual-device-listener.c:153 296s (process:2466): libfprint-device-DEBUG: 05:01:55.823: Device reported open completion 296s (process:2466): libfprint-device-DEBUG: 05:01:55.823: Completing action FPI_DEVICE_ACTION_OPEN in idle! 296s (process:2466): libfprint-device-DEBUG: 05:01:55.823: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.824: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.824: Got instructions of length 19 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.824: Received command SET_SCAN_TYPE press 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.824: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.825: Got instructions of length 19 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.825: Received command SET_SCAN_TYPE swipe 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.825: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.825: Got instructions of length 25 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.825: Received command SET_SCAN_TYPE eye-contact 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.825: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.825: Got instructions of length 16 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.825: Received command SET_KEEP_ALIVE 0 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.825: Keep alive toggled: 0 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.826: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.826: Got instructions of length 19 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.826: Received command SET_ENROLL_STAGES 5 296s (process:2466): libfprint-device-DEBUG: 05:01:55.826: Device reported close completion 296s (process:2466): libfprint-device-DEBUG: 05:01:55.826: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 296s (process:2466): libfprint-device-DEBUG: 05:01:55.826: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 296s ok 296s test_close_error (__main__.VirtualDevice.test_close_error) ... (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.826: 73744579: ../libfprint/drivers/virtual-device.c:387 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.826: 73744600: ../libfprint/drivers/virtual-device-listener.c:153 296s (process:2466): libfprint-device-DEBUG: 05:01:55.826: Device reported open completion 296s (process:2466): libfprint-device-DEBUG: 05:01:55.826: Completing action FPI_DEVICE_ACTION_OPEN in idle! 296s (process:2466): libfprint-device-DEBUG: 05:01:55.826: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.826: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.826: Got instructions of length 9 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.826: Received command SLEEP 100 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.827: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.827: Got instructions of length 7 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.827: Received command ERROR 4 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.827: Processing command SLEEP 100 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.827: Sleeping 100ms 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.927: Sleeping completed 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.927: Processing command ERROR 4 296s (process:2466): libfprint-device-DEBUG: 05:01:55.927: Device reported close completion 296s (process:2466): libfprint-device-DEBUG: 05:01:55.927: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 296s (process:2466): libfprint-device-DEBUG: 05:01:55.927: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 296s ok 296s test_close_while_opening (__main__.VirtualDevice.test_close_while_opening) ... (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.928: 73846686: ../libfprint/drivers/virtual-device.c:387 296s (process:2466): libfprint-device-DEBUG: 05:01:55.928: Device reported open completion 296s (process:2466): libfprint-device-DEBUG: 05:01:55.928: Completing action FPI_DEVICE_ACTION_OPEN in idle! 296s (process:2466): libfprint-device-DEBUG: 05:01:55.928: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.928: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.928: Got instructions of length 16 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.928: Received command SET_KEEP_ALIVE 1 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.928: Keep alive toggled: 1 296s (process:2466): libfprint-device-DEBUG: 05:01:55.928: Device reported close completion 296s (process:2466): libfprint-device-DEBUG: 05:01:55.929: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 296s (process:2466): libfprint-device-DEBUG: 05:01:55.929: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 296s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:55.929: Got a new connection! 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.929: Got instructions of length 9 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.929: Received command SLEEP 500 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.929: 73847750: ../libfprint/drivers/virtual-device.c:387 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.929: Processing command SLEEP 500 296s (process:2466): libfprint-virtual_device-DEBUG: 05:01:55.929: Sleeping 500ms 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.430: Sleeping completed 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.430: 74348466: ../libfprint/drivers/virtual-device.c:387 297s (process:2466): libfprint-device-DEBUG: 05:01:56.430: Device reported open completion 297s (process:2466): libfprint-device-DEBUG: 05:01:56.430: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s (process:2466): libfprint-device-DEBUG: 05:01:56.430: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:56.431: Got a new connection! 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.431: Got instructions of length 16 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.431: Received command SET_KEEP_ALIVE 0 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.431: Keep alive toggled: 0 297s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:56.431: Got a new connection! 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.431: Got instructions of length 19 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.431: Received command SET_ENROLL_STAGES 5 297s (process:2466): libfprint-device-DEBUG: 05:01:56.431: Device reported close completion 297s (process:2466): libfprint-device-DEBUG: 05:01:56.431: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s (process:2466): libfprint-device-DEBUG: 05:01:56.431: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s ok 297s test_delayed_open (__main__.VirtualDevice.test_delayed_open) ... (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.431: 74350092: ../libfprint/drivers/virtual-device.c:387 297s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:56.431: 74350107: ../libfprint/drivers/virtual-device-listener.c:153 297s (process:2466): libfprint-device-DEBUG: 05:01:56.432: Device reported open completion 297s (process:2466): libfprint-device-DEBUG: 05:01:56.432: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s (process:2466): libfprint-device-DEBUG: 05:01:56.432: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:56.432: Got a new connection! 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.432: Got instructions of length 16 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.432: Received command IGNORED_COMMAND 297s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:56.432: Got a new connection! 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.432: Got instructions of length 9 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.432: Received command SLEEP 500 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.432: Processing command IGNORED_COMMAND 297s (process:2466): libfprint-device-DEBUG: 05:01:56.432: Device reported close completion 297s (process:2466): libfprint-device-DEBUG: 05:01:56.432: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s (process:2466): libfprint-device-DEBUG: 05:01:56.432: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.434: 74352588: ../libfprint/drivers/virtual-device.c:387 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.434: Processing command SLEEP 500 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.434: Sleeping 500ms 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.935: Sleeping completed 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.935: 74853318: ../libfprint/drivers/virtual-device.c:387 297s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:56.935: 74853333: ../libfprint/drivers/virtual-device-listener.c:153 297s (process:2466): libfprint-device-DEBUG: 05:01:56.935: Device reported open completion 297s (process:2466): libfprint-device-DEBUG: 05:01:56.935: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s (process:2466): libfprint-device-DEBUG: 05:01:56.935: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:56.935: Got a new connection! 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.935: Got instructions of length 16 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.935: Received command SET_KEEP_ALIVE 0 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.935: Keep alive toggled: 0 297s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:56.936: Got a new connection! 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.936: Got instructions of length 19 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.936: Received command SET_ENROLL_STAGES 5 297s (process:2466): libfprint-device-DEBUG: 05:01:56.936: Device reported close completion 297s (process:2466): libfprint-device-DEBUG: 05:01:56.936: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s (process:2466): libfprint-device-DEBUG: 05:01:56.936: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s ok 297s test_delayed_open_with_keep_alive (__main__.VirtualDevice.test_delayed_open_with_keep_alive) ... (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.936: 74854823: ../libfprint/drivers/virtual-device.c:387 297s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:56.936: 74854835: ../libfprint/drivers/virtual-device-listener.c:153 297s (process:2466): libfprint-device-DEBUG: 05:01:56.936: Device reported open completion 297s (process:2466): libfprint-device-DEBUG: 05:01:56.937: Completing action FPI_DEVICE_ACTION_OPEN in idle! 297s (process:2466): libfprint-device-DEBUG: 05:01:56.937: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:56.937: Got a new connection! 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.937: Got instructions of length 16 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.937: Received command SET_KEEP_ALIVE 1 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.937: Keep alive toggled: 1 297s (process:2466): libfprint-device-DEBUG: 05:01:56.937: Device reported close completion 297s (process:2466): libfprint-device-DEBUG: 05:01:56.937: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 297s (process:2466): libfprint-device-DEBUG: 05:01:56.937: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 297s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:56.937: Got a new connection! 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.937: Got instructions of length 9 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.937: Received command SLEEP 500 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.937: 74855973: ../libfprint/drivers/virtual-device.c:387 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.937: Processing command SLEEP 500 297s (process:2466): libfprint-virtual_device-DEBUG: 05:01:56.937: Sleeping 500ms 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.438: Sleeping completed 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.438: 75356845: ../libfprint/drivers/virtual-device.c:387 298s (process:2466): libfprint-device-DEBUG: 05:01:57.438: Device reported open completion 298s (process:2466): libfprint-device-DEBUG: 05:01:57.438: Completing action FPI_DEVICE_ACTION_OPEN in idle! 298s (process:2466): libfprint-device-DEBUG: 05:01:57.438: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.439: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.439: Got instructions of length 16 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.439: Received command SET_KEEP_ALIVE 0 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.439: Keep alive toggled: 0 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.439: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.439: Got instructions of length 19 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.439: Received command SET_ENROLL_STAGES 5 298s (process:2466): libfprint-device-DEBUG: 05:01:57.439: Device reported close completion 298s (process:2466): libfprint-device-DEBUG: 05:01:57.439: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 298s (process:2466): libfprint-device-DEBUG: 05:01:57.439: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 298s ok 298s test_device_features (__main__.VirtualDevice.test_device_features) ... (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.439: 75358138: ../libfprint/drivers/virtual-device.c:387 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.439: 75358163: ../libfprint/drivers/virtual-device-listener.c:153 298s (process:2466): libfprint-device-DEBUG: 05:01:57.440: Device reported open completion 298s (process:2466): libfprint-device-DEBUG: 05:01:57.440: Completing action FPI_DEVICE_ACTION_OPEN in idle! 298s (process:2466): libfprint-device-DEBUG: 05:01:57.440: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.440: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.440: Got instructions of length 16 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.440: Received command SET_KEEP_ALIVE 0 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.440: Keep alive toggled: 0 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.440: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.441: Got instructions of length 19 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.441: Received command SET_ENROLL_STAGES 5 298s (process:2466): libfprint-device-DEBUG: 05:01:57.441: Device reported close completion 298s (process:2466): libfprint-device-DEBUG: 05:01:57.441: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 298s (process:2466): libfprint-device-DEBUG: 05:01:57.441: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 298s ok 298s test_device_properties (__main__.VirtualDevice.test_device_properties) ... (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.441: 75359611: ../libfprint/drivers/virtual-device.c:387 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.441: 75359623: ../libfprint/drivers/virtual-device-listener.c:153 298s (process:2466): libfprint-device-DEBUG: 05:01:57.441: Device reported open completion 298s (process:2466): libfprint-device-DEBUG: 05:01:57.441: Completing action FPI_DEVICE_ACTION_OPEN in idle! 298s (process:2466): libfprint-device-DEBUG: 05:01:57.441: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 298s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:463: DeprecationWarning: FPrint.Device.supports_identify is deprecated 298s self.assertFalse(self.dev.supports_identify()) 298s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:464: DeprecationWarning: FPrint.Device.supports_capture is deprecated 298s self.assertFalse(self.dev.supports_capture()) 298s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:465: DeprecationWarning: FPrint.Device.has_storage is deprecated 298s self.assertFalse(self.dev.has_storage()) 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.442: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.442: Got instructions of length 16 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.442: Received command SET_KEEP_ALIVE 0 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.442: Keep alive toggled: 0 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.442: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.442: Got instructions of length 19 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.442: Received command SET_ENROLL_STAGES 5 298s (process:2466): libfprint-device-DEBUG: 05:01:57.442: Device reported close completion 298s (process:2466): libfprint-device-DEBUG: 05:01:57.442: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 298s (process:2466): libfprint-device-DEBUG: 05:01:57.442: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 298s ok 298s test_device_sleep (__main__.VirtualDevice.test_device_sleep) ... (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.442: 75361148: ../libfprint/drivers/virtual-device.c:387 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.442: 75361162: ../libfprint/drivers/virtual-device-listener.c:153 298s (process:2466): libfprint-device-DEBUG: 05:01:57.443: Device reported open completion 298s (process:2466): libfprint-device-DEBUG: 05:01:57.443: Completing action FPI_DEVICE_ACTION_OPEN in idle! 298s (process:2466): libfprint-device-DEBUG: 05:01:57.443: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.443: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.443: Got instructions of length 10 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.443: Received command SLEEP 1500 298s (process:2466): libfprint-device-DEBUG: 05:01:57.444: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.444: Processing command SLEEP 1500 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.444: Sleeping 1500ms 298s (process:2466): libfprint-device-DEBUG: 05:01:57.743: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 298s (process:2466): libfprint-device-DEBUG: 05:01:57.744: Idle cancelling on ongoing operation! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.744: Got cancellation! 298s (process:2466): libfprint-device-DEBUG: 05:01:57.744: Device reported finger status change: FP_FINGER_STATUS_NEEDED 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.744: Virtual device scan failed with error: Operation was cancelled 298s (process:2466): libfprint-device-DEBUG: 05:01:57.744: Device reported verify completion 298s (process:2466): libfprint-device-DEBUG: 05:01:57.744: Device reported finger status change: FP_FINGER_STATUS_NONE 298s (process:2466): libfprint-device-DEBUG: 05:01:57.744: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 298s (process:2466): libfprint-device-DEBUG: 05:01:57.744: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.944: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.944: Got instructions of length 16 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.944: Received command SET_KEEP_ALIVE 0 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.944: Keep alive toggled: 0 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.944: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.944: Got instructions of length 19 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.944: Received command SET_ENROLL_STAGES 5 298s (process:2466): libfprint-device-DEBUG: 05:01:57.945: Device reported close completion 298s (process:2466): libfprint-device-DEBUG: 05:01:57.945: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 298s (process:2466): libfprint-device-DEBUG: 05:01:57.945: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 298s ok 298s test_device_sleep_before_completing_verify (__main__.VirtualDevice.test_device_sleep_before_completing_verify) ... (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.945: 75863436: ../libfprint/drivers/virtual-device.c:387 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.945: 75863486: ../libfprint/drivers/virtual-device-listener.c:153 298s (process:2466): libfprint-device-DEBUG: 05:01:57.945: Device reported open completion 298s (process:2466): libfprint-device-DEBUG: 05:01:57.945: Completing action FPI_DEVICE_ACTION_OPEN in idle! 298s (process:2466): libfprint-device-DEBUG: 05:01:57.945: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.945: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.946: Got instructions of length 14 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.946: Received command SCAN foo-print 298s (process:2466): libfprint-device-DEBUG: 05:01:57.946: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.946: Processing command SCAN foo-print 298s (process:2466): libfprint-device-DEBUG: 05:01:57.946: Device reported finger status change: FP_FINGER_STATUS_NEEDED 298s (process:2466): libfprint-device-DEBUG: 05:01:57.946: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 298s (process:2466): libfprint-device-DEBUG: 05:01:57.946: Device reported finger status change: FP_FINGER_STATUS_NEEDED 298s (process:2466): libfprint-device-DEBUG: 05:01:57.946: Device reported enroll progress, reported 1 of 5 have been completed 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.946: Sleeping completed 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.946: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.946: Got instructions of length 14 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.946: Received command SCAN foo-print 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.946: Processing command SCAN foo-print 298s (process:2466): libfprint-device-DEBUG: 05:01:57.946: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 298s (process:2466): libfprint-device-DEBUG: 05:01:57.946: Device reported finger status change: FP_FINGER_STATUS_NEEDED 298s (process:2466): libfprint-device-DEBUG: 05:01:57.946: Device reported enroll progress, reported 2 of 5 have been completed 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.947: Sleeping completed 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.947: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.947: Got instructions of length 14 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.947: Received command SCAN foo-print 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.947: Processing command SCAN foo-print 298s (process:2466): libfprint-device-DEBUG: 05:01:57.947: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 298s (process:2466): libfprint-device-DEBUG: 05:01:57.947: Device reported finger status change: FP_FINGER_STATUS_NEEDED 298s (process:2466): libfprint-device-DEBUG: 05:01:57.947: Device reported enroll progress, reported 3 of 5 have been completed 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.947: Sleeping completed 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.947: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.947: Got instructions of length 14 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.947: Received command SCAN foo-print 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.947: Processing command SCAN foo-print 298s (process:2466): libfprint-device-DEBUG: 05:01:57.947: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 298s (process:2466): libfprint-device-DEBUG: 05:01:57.947: Device reported finger status change: FP_FINGER_STATUS_NEEDED 298s (process:2466): libfprint-device-DEBUG: 05:01:57.947: Device reported enroll progress, reported 4 of 5 have been completed 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.947: Sleeping completed 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.947: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.948: Got instructions of length 14 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.948: Received command SCAN foo-print 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.948: Processing command SCAN foo-print 298s (process:2466): libfprint-device-DEBUG: 05:01:57.948: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 298s (process:2466): libfprint-device-DEBUG: 05:01:57.948: Device reported finger status change: FP_FINGER_STATUS_NEEDED 298s (process:2466): libfprint-device-DEBUG: 05:01:57.948: Device reported enroll progress, reported 5 of 5 have been completed 298s (process:2466): libfprint-device-DEBUG: 05:01:57.948: Device reported enroll completion 298s (process:2466): libfprint-device-DEBUG: 05:01:57.948: Device reported finger status change: FP_FINGER_STATUS_NONE 298s (process:2466): libfprint-device-DEBUG: 05:01:57.948: Print for finger FP_FINGER_LEFT_RING enrolled 298s (process:2466): libfprint-device-DEBUG: 05:01:57.948: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 298s (process:2466): libfprint-device-DEBUG: 05:01:57.948: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.948: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.948: Got instructions of length 9 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.948: Received command SLEEP 100 298s (process:2466): libfprint-device-DEBUG: 05:01:57.948: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.948: Processing command SLEEP 100 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.948: Sleeping 100ms 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.949: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.949: Got instructions of length 14 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.949: Received command SCAN bar-print 298s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:57.949: Got a new connection! 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.949: Got instructions of length 9 298s (process:2466): libfprint-virtual_device-DEBUG: 05:01:57.949: Received command SLEEP 800 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.048: Sleeping completed 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.048: Processing command SCAN bar-print 299s (process:2466): libfprint-device-DEBUG: 05:01:58.049: Device reported finger status change: FP_FINGER_STATUS_NEEDED 299s (process:2466): libfprint-device-DEBUG: 05:01:58.049: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.049: Virtual device scanned print bar-print 299s (process:2466): libfprint-device-DEBUG: 05:01:58.049: Device reported verify result 299s (process:2466): libfprint-device-DEBUG: 05:01:58.049: Device reported finger status change: FP_FINGER_STATUS_NEEDED 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.049: Processing command SLEEP 800 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.049: Sleeping 800ms 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.049: Sleeping now, command queued for later: SCAN bar-print 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.849: Sleeping completed 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.849: Processing command SCAN bar-print 299s (process:2466): libfprint-device-DEBUG: 05:01:58.849: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.849: Virtual device scanned print bar-print 299s (process:2466): libfprint-device-DEBUG: 05:01:58.850: Device reported finger status change: FP_FINGER_STATUS_NEEDED 299s (process:2466): libfprint-device-DEBUG: 05:01:58.850: Device reported verify completion 299s (process:2466): libfprint-device-DEBUG: 05:01:58.850: Device reported finger status change: FP_FINGER_STATUS_NONE 299s (process:2466): libfprint-device-DEBUG: 05:01:58.850: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 299s (process:2466): libfprint-device-DEBUG: 05:01:58.850: Updated temperature model after 0.90 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 299s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:58.850: Got a new connection! 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.850: Got instructions of length 16 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.850: Received command SET_KEEP_ALIVE 0 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.850: Keep alive toggled: 0 299s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:58.850: Got a new connection! 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.850: Got instructions of length 19 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.850: Received command SET_ENROLL_STAGES 5 299s (process:2466): libfprint-device-DEBUG: 05:01:58.850: Device reported close completion 299s (process:2466): libfprint-device-DEBUG: 05:01:58.850: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 299s (process:2466): libfprint-device-DEBUG: 05:01:58.850: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 299s Enroll done 299s ok 299s test_device_sleep_on_cancellation (__main__.VirtualDevice.test_device_sleep_on_cancellation) ... (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.851: 76769254: ../libfprint/drivers/virtual-device.c:387 299s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:58.851: 76769271: ../libfprint/drivers/virtual-device-listener.c:153 299s (process:2466): libfprint-device-DEBUG: 05:01:58.851: Device reported open completion 299s (process:2466): libfprint-device-DEBUG: 05:01:58.851: Completing action FPI_DEVICE_ACTION_OPEN in idle! 299s (process:2466): libfprint-device-DEBUG: 05:01:58.851: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 299s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:58.851: Got a new connection! 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.851: Got instructions of length 26 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.851: Received command SET_CANCELLATION_ENABLED 0 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.851: Cancellation support toggled: 0 299s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:58.851: Got a new connection! 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.852: Got instructions of length 10 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.852: Received command SLEEP 1500 299s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:01:58.852: Got a new connection! 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.852: Got instructions of length 14 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.852: Received command SCAN foo-print 299s (process:2466): libfprint-device-DEBUG: 05:01:58.852: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.852: Processing command SLEEP 1500 299s (process:2466): libfprint-virtual_device-DEBUG: 05:01:58.852: Sleeping 1500ms 300s Executing: libfprint-2/virtual-device.test 300s (process:2466): libfprint-device-DEBUG: 05:01:59.152: Idle cancelling on ongoing operation! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.353: Sleeping completed 301s (process:2466): libfprint-device-DEBUG: 05:02:00.353: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.353: Virtual device scan failed with error: Operation was cancelled 301s (process:2466): libfprint-device-DEBUG: 05:02:00.353: Device reported verify completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.353: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.353: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.353: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.353: Processing command SCAN foo-print 301s (process:2466): libfprint-device-DEBUG: 05:02:00.353: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.354: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.354: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s ok 301s test_enroll (__main__.VirtualDevice.test_enroll) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.354: 78272525: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.354: 78272543: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.354: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.354: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.354: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.354: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.354: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.354: Received command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.354: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.354: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.355: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.355: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.355: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.355: Device reported enroll progress, reported 1 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.355: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.355: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.355: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.355: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.355: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.355: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.355: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.355: Device reported enroll progress, reported 2 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.355: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.355: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.355: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.355: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.355: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.355: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.355: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.355: Device reported enroll progress, reported 3 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.355: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.355: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.355: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.355: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.355: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.355: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.355: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.355: Device reported enroll progress, reported 4 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.355: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.356: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.356: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.356: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.356: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.356: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.356: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.356: Device reported enroll progress, reported 5 of 5 have been completed 301s (process:2466): libfprint-device-DEBUG: 05:02:00.356: Device reported enroll completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.356: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.356: Print for finger FP_FINGER_LEFT_LITTLE enrolled 301s (process:2466): libfprint-device-DEBUG: 05:02:00.356: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.356: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.357: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.357: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.357: Received command SET_KEEP_ALIVE 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.357: Keep alive toggled: 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.357: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.357: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.357: Received command SET_ENROLL_STAGES 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.357: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.357: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.357: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s Enroll done 301s ok 301s test_enroll_script (__main__.VirtualDevice.test_enroll_script) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.358: 78276209: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.358: 78276246: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.358: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.358: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.358: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.358: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.358: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.358: Received command SET_ENROLL_STAGES 8 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.358: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.358: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.358: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.359: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.359: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.359: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.359: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.359: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.359: Received command RETRY 1 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.359: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.359: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.359: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.359: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.359: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.360: Received command RETRY 3 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.360: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.360: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.360: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.360: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.360: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.360: Received command RETRY 2 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.360: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.360: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.360: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.360: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.361: Got instructions of length 8 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.361: Received command SLEEP 10 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.361: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.361: Got instructions of length 8 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.361: Received command SLEEP 20 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.361: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.361: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.361: Received command RETRY 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.361: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.361: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.361: Received command RETRY 3 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.361: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.362: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.362: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.362: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.362: Got instructions of length 15 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.362: Received command SCAN another-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.362: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.362: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.362: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.362: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.362: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.362: Received command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported enroll progress, reported 1 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported enroll progress, reported 2 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Processing command RETRY 1 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported enroll progress, reported 2 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported enroll progress, reported 3 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Processing command RETRY 3 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported enroll progress, reported 3 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported enroll progress, reported 4 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Processing command RETRY 2 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported enroll progress, reported 4 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.363: Device reported enroll progress, reported 5 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Processing command SLEEP 10 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.363: Sleeping 10ms 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.373: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.373: Processing command SLEEP 20 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.373: Sleeping 20ms 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.393: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.393: Processing command RETRY 0 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Device reported enroll progress, reported 5 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.393: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.393: Processing command RETRY 3 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Device reported enroll progress, reported 5 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.393: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.393: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Device reported enroll progress, reported 6 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.393: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.393: Processing command SCAN another-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Device reported enroll progress, reported 6 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.393: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.393: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Device reported enroll progress, reported 7 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.393: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.393: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Device reported enroll progress, reported 8 of 8 have been completed 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Device reported enroll completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Print for finger FP_FINGER_UNKNOWN enrolled 301s (process:2466): libfprint-device-DEBUG: 05:02:00.393: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.394: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.394: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.394: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.394: Received command SET_KEEP_ALIVE 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.394: Keep alive toggled: 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.394: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.394: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.394: Received command SET_ENROLL_STAGES 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.394: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.394: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.394: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s ok 301s test_enroll_script_interactive (__main__.VirtualDevice.test_enroll_script_interactive) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.394: 78312880: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.394: 78312888: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.394: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.394: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.394: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.395: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.395: Got instructions of length 8 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.395: Received command SLEEP 50 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.395: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.395: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.395: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.395: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.395: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.395: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.395: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.395: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.395: Received command RETRY 1 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.395: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.396: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.396: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.396: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.396: Got instructions of length 8 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.396: Received command SLEEP 50 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.396: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.396: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.396: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.396: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.396: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.396: Received command RETRY 2 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.396: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.396: Got instructions of length 15 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.396: Received command SCAN another-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.396: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.396: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.396: Received command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.396: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.396: Processing command SLEEP 50 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.396: Sleeping 50ms 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.447: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.447: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.447: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.447: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.447: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.447: Device reported enroll progress, reported 1 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.447: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.447: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.447: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.447: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.447: Device reported enroll progress, reported 2 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.447: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.447: Processing command RETRY 1 301s (process:2466): libfprint-device-DEBUG: 05:02:00.447: Device reported enroll progress, reported 2 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.447: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.447: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.447: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.447: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.447: Device reported enroll progress, reported 3 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.447: Processing command SLEEP 50 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.447: Sleeping 50ms 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.497: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.497: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.497: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.497: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.497: Device reported enroll progress, reported 4 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.497: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.497: Processing command RETRY 2 301s (process:2466): libfprint-device-DEBUG: 05:02:00.497: Device reported enroll progress, reported 4 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.497: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.497: Processing command SCAN another-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.497: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.497: Device reported enroll progress, reported 4 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.497: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.497: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.497: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.497: Device reported enroll progress, reported 5 of 5 have been completed 301s (process:2466): libfprint-device-DEBUG: 05:02:00.497: Device reported enroll completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.497: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.497: Print for finger FP_FINGER_UNKNOWN enrolled 301s (process:2466): libfprint-device-DEBUG: 05:02:00.497: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.497: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.498: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.498: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.498: Received command SET_KEEP_ALIVE 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.498: Keep alive toggled: 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.498: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.498: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.498: Received command SET_ENROLL_STAGES 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.498: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.498: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.498: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s ok 301s test_enroll_verify_error (__main__.VirtualDevice.test_enroll_verify_error) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.498: 78416959: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.498: 78416981: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.499: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.499: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.499: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.499: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.499: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.499: Received command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.499: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.499: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.499: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.499: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.499: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.499: Device reported enroll progress, reported 1 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.499: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.499: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.499: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.499: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.499: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.499: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.499: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.499: Device reported enroll progress, reported 2 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.499: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.500: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.500: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.500: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.500: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.500: Device reported enroll progress, reported 3 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.500: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.500: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.500: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.500: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.500: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.500: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.500: Device reported enroll progress, reported 4 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.500: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.500: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.501: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.501: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.501: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.501: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.501: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.501: Device reported enroll progress, reported 5 of 5 have been completed 301s (process:2466): libfprint-device-DEBUG: 05:02:00.501: Device reported enroll completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.501: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.501: Print for finger FP_FINGER_LEFT_RING enrolled 301s (process:2466): libfprint-device-DEBUG: 05:02:00.501: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.501: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.501: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.501: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.501: Received command ERROR 0 301s (process:2466): libfprint-device-DEBUG: 05:02:00.501: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.501: Processing command ERROR 0 301s (process:2466): libfprint-device-DEBUG: 05:02:00.501: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.501: Virtual device scan failed with error: An unspecified error occurred! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.501: Device reported verify completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.501: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.501: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.501: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.501: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.501: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.501: Received command SET_KEEP_ALIVE 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.501: Keep alive toggled: 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.501: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.502: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.502: Received command SET_ENROLL_STAGES 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.502: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.502: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.502: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s Enroll done 301s ok 301s test_enroll_verify_match (__main__.VirtualDevice.test_enroll_verify_match) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.502: 78420445: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.502: 78420459: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.502: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.502: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.502: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.502: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.502: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.502: Received command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.502: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.502: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.502: Device reported enroll progress, reported 1 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.502: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.502: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.502: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.502: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.502: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.502: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Device reported enroll progress, reported 2 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.503: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.503: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.503: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.503: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.503: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Device reported enroll progress, reported 3 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.503: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.503: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.503: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.503: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.503: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Device reported enroll progress, reported 4 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.503: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.503: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.503: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.503: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.503: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Device reported enroll progress, reported 5 of 5 have been completed 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Device reported enroll completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Print for finger FP_FINGER_LEFT_THUMB enrolled 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.503: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.504: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.504: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.504: Received command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.505: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.505: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.505: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.505: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.505: Virtual device scanned print testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.505: Device reported verify result 301s (process:2466): libfprint-device-DEBUG: 05:02:00.505: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.505: Device reported verify completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.505: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.505: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.505: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.506: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.506: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.506: Received command SET_KEEP_ALIVE 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.506: Keep alive toggled: 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.506: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.506: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.506: Received command SET_ENROLL_STAGES 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.506: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.506: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.506: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s Enroll done 301s ok 301s test_enroll_verify_no_match (__main__.VirtualDevice.test_enroll_verify_no_match) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.506: 78424747: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.506: 78424757: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.506: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.506: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.506: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.507: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.507: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.507: Received command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.510: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.510: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.510: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.510: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.510: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.510: Device reported enroll progress, reported 1 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.511: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.511: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.511: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.511: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.511: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.511: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.511: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.511: Device reported enroll progress, reported 2 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.511: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.513: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.513: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.513: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.513: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.513: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.513: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.513: Device reported enroll progress, reported 3 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.513: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.514: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.514: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.514: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.514: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.514: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.514: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.514: Device reported enroll progress, reported 4 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.514: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.516: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.516: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.516: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.516: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.516: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.516: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.516: Device reported enroll progress, reported 5 of 5 have been completed 301s (process:2466): libfprint-device-DEBUG: 05:02:00.516: Device reported enroll completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.516: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.516: Print for finger FP_FINGER_LEFT_RING enrolled 301s (process:2466): libfprint-device-DEBUG: 05:02:00.516: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.516: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.516: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.516: Got instructions of length 18 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.516: Received command SCAN not-testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.519: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.519: Processing command SCAN not-testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.519: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.519: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.519: Virtual device scanned print not-testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.519: Device reported verify result 301s (process:2466): libfprint-device-DEBUG: 05:02:00.519: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.519: Device reported verify completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.519: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.519: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.519: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.519: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.520: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.520: Received command SET_KEEP_ALIVE 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.520: Keep alive toggled: 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.520: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.520: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.520: Received command SET_ENROLL_STAGES 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.520: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.520: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.520: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s Enroll done 301s ok 301s test_enroll_verify_retry (__main__.VirtualDevice.test_enroll_verify_retry) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.520: 78438580: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.520: 78438590: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.520: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.520: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.520: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.520: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.520: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.520: Received command RETRY 1 301s (process:2466): libfprint-device-DEBUG: 05:02:00.524: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.524: Processing command RETRY 1 301s (process:2466): libfprint-device-DEBUG: 05:02:00.524: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.524: Virtual device scan failed with error: The swipe was too short, please try again. 301s (process:2466): libfprint-device-DEBUG: 05:02:00.524: Device reported verify result 301s (process:2466): libfprint-device-DEBUG: 05:02:00.524: Device reported verify completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.524: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.524: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.524: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.524: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.524: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.524: Received command SET_KEEP_ALIVE 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.524: Keep alive toggled: 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.524: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.524: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.524: Received command SET_ENROLL_STAGES 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.525: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.525: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.525: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s ok 301s test_enroll_verify_script (__main__.VirtualDevice.test_enroll_verify_script) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.525: 78443381: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.525: 78443410: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.525: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.525: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.525: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.525: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.525: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.525: Received command SET_ENROLL_STAGES 8 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.525: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.525: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.525: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.526: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.526: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.526: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.526: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.526: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.526: Received command RETRY 1 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.526: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.526: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.526: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.526: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.526: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.526: Received command RETRY 3 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.526: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.526: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.526: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.526: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.526: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.526: Received command RETRY 2 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.531: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.531: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.531: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.531: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.531: Got instructions of length 8 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.531: Received command SLEEP 10 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.531: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.531: Got instructions of length 8 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.531: Received command SLEEP 20 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.531: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.531: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.531: Received command RETRY 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.531: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Received command RETRY 3 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.532: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.532: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Got instructions of length 15 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Received command SCAN another-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.532: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Received command SCAN print-id 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.532: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Received command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported enroll progress, reported 1 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported enroll progress, reported 2 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Processing command RETRY 1 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported enroll progress, reported 2 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported enroll progress, reported 3 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Processing command RETRY 3 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported enroll progress, reported 3 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported enroll progress, reported 4 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Processing command RETRY 2 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported enroll progress, reported 4 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.532: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.533: Device reported enroll progress, reported 5 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.533: Processing command SLEEP 10 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.533: Sleeping 10ms 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.543: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.543: Processing command SLEEP 20 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.543: Sleeping 20ms 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.563: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.563: Processing command RETRY 0 301s (process:2466): libfprint-device-DEBUG: 05:02:00.563: Device reported enroll progress, reported 5 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.563: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.563: Processing command RETRY 3 301s (process:2466): libfprint-device-DEBUG: 05:02:00.563: Device reported enroll progress, reported 5 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.563: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.563: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.563: Device reported enroll progress, reported 6 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.563: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.563: Processing command SCAN another-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.563: Device reported enroll progress, reported 6 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.563: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.563: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.563: Device reported enroll progress, reported 7 of 8 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.563: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.563: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.564: Device reported enroll progress, reported 8 of 8 have been completed 301s (process:2466): libfprint-device-DEBUG: 05:02:00.564: Device reported enroll completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.564: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.564: Print for finger FP_FINGER_UNKNOWN enrolled 301s (process:2466): libfprint-device-DEBUG: 05:02:00.564: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.564: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.564: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.564: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.564: Received command RETRY 2 301s (process:2466): libfprint-device-DEBUG: 05:02:00.564: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.564: Processing command RETRY 2 301s (process:2466): libfprint-device-DEBUG: 05:02:00.564: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.564: Virtual device scan failed with error: The finger was not centered properly, please try again. 301s (process:2466): libfprint-device-DEBUG: 05:02:00.564: Device reported verify result 301s (process:2466): libfprint-device-DEBUG: 05:02:00.564: Device reported verify completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.564: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.564: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.564: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.565: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.565: Got instructions of length 8 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.565: Received command SLEEP 50 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.565: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.565: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.565: Received command RETRY 1 301s (process:2466): libfprint-device-DEBUG: 05:02:00.565: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.565: Processing command SLEEP 50 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.565: Sleeping 50ms 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.615: Sleeping completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.615: Processing command RETRY 1 301s (process:2466): libfprint-device-DEBUG: 05:02:00.615: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.615: Virtual device scan failed with error: The swipe was too short, please try again. 301s (process:2466): libfprint-device-DEBUG: 05:02:00.615: Device reported verify result 301s (process:2466): libfprint-device-DEBUG: 05:02:00.615: Device reported verify completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.615: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.615: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.615: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.616: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.616: Got instructions of length 15 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.616: Received command SCAN another-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.616: Processing command SCAN another-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.616: Virtual device scanned print another-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Device reported verify result 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Device reported verify completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.616: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.616: Got instructions of length 13 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.616: Received command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.616: Processing command SCAN print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.616: Virtual device scanned print print-id 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Device reported verify result 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Device reported verify completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.616: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.617: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.617: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.617: Received command SET_KEEP_ALIVE 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.617: Keep alive toggled: 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.617: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.617: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.617: Received command SET_ENROLL_STAGES 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.617: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.617: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.617: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s ok 301s test_enroll_with_retry (__main__.VirtualDevice.test_enroll_with_retry) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.617: 78535927: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.617: 78535942: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.617: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.617: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.618: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.618: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.618: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.618: Received command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.618: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.618: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.618: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.618: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.618: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.618: Device reported enroll progress, reported 1 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.618: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.618: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.618: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.619: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.619: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.619: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.619: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.619: Device reported enroll progress, reported 2 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.619: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.619: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.619: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.619: Received command RETRY 1 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.619: Processing command RETRY 1 301s (process:2466): libfprint-device-DEBUG: 05:02:00.619: Device reported enroll progress, reported 2 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.619: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.619: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.620: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.620: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.620: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.620: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.620: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.620: Device reported enroll progress, reported 3 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.620: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.620: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.620: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.620: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.621: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.621: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.621: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.621: Device reported enroll progress, reported 4 of 5 have been completed 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.621: Sleeping completed 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.621: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.621: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.621: Received command SCAN testprint 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.621: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.621: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.621: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.621: Device reported enroll progress, reported 5 of 5 have been completed 301s (process:2466): libfprint-device-DEBUG: 05:02:00.621: Device reported enroll completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.621: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.621: Print for finger FP_FINGER_LEFT_LITTLE enrolled 301s (process:2466): libfprint-device-DEBUG: 05:02:00.621: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.621: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.621: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.622: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.622: Received command SET_KEEP_ALIVE 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.622: Keep alive toggled: 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.622: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.622: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.622: Received command SET_ENROLL_STAGES 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.622: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.622: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.622: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s Enroll done 301s ok 301s test_finger_status (__main__.VirtualDevice.test_finger_status) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.622: 78540685: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.622: 78540699: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.622: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.622: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.622: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-device-DEBUG: 05:02:00.622: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-device-DEBUG: 05:02:00.622: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.623: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.623: Got instructions of length 8 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.623: Received command FINGER 1 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.623: Processing command FINGER 1 301s (process:2466): libfprint-device-DEBUG: 05:02:00.623: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.623: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.623: Got instructions of length 8 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.623: Received command FINGER 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.623: Processing command FINGER 0 301s (process:2466): libfprint-device-DEBUG: 05:02:00.623: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.623: Idle cancelling on ongoing operation! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.623: Got cancellation! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.623: Virtual device scan failed with error: Operation was cancelled 301s (process:2466): libfprint-device-DEBUG: 05:02:00.623: Device reported verify completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.623: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.623: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.623: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.623: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.623: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.623: Received command SET_KEEP_ALIVE 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.623: Keep alive toggled: 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.623: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.623: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.624: Received command SET_ENROLL_STAGES 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.624: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.624: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.624: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s ok 301s test_finger_status_after_sleep (__main__.VirtualDevice.test_finger_status_after_sleep) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.624: 78542389: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.624: 78542401: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.624: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.624: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.624: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.624: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.624: Got instructions of length 8 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.624: Received command SLEEP 10 301s (process:2466): libfprint-device-DEBUG: 05:02:00.624: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.624: Processing command SLEEP 10 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.624: Sleeping 10ms 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.634: Sleeping completed 301s (process:2466): libfprint-device-DEBUG: 05:02:00.634: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.635: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.635: Got instructions of length 8 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.635: Received command FINGER 1 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.635: Processing command FINGER 1 301s (process:2466): libfprint-device-DEBUG: 05:02:00.635: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.635: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.635: Got instructions of length 8 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.635: Received command FINGER 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.635: Processing command FINGER 0 301s (process:2466): libfprint-device-DEBUG: 05:02:00.635: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.635: Idle cancelling on ongoing operation! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.635: Got cancellation! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.635: Virtual device scan failed with error: Operation was cancelled 301s (process:2466): libfprint-device-DEBUG: 05:02:00.635: Device reported verify completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.635: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.635: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.635: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.635: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.635: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.635: Received command SET_KEEP_ALIVE 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.635: Keep alive toggled: 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.636: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.636: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.636: Received command SET_ENROLL_STAGES 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.636: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.636: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.636: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s ok 301s test_identify_unsupported (__main__.VirtualDevice.test_identify_unsupported) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.636: 78554511: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.636: 78554524: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.636: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.636: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.636: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.636: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.637: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.637: Received command SET_KEEP_ALIVE 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.637: Keep alive toggled: 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.637: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.637: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.637: Received command SET_ENROLL_STAGES 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.637: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.637: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.637: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s ok 301s test_open_error (__main__.VirtualDevice.test_open_error) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.637: 78555605: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.637: 78555619: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.637: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.637: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.637: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.637: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.637: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.637: Received command IGNORED_COMMAND 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.637: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.637: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.637: Received command ERROR 5 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.638: Processing command IGNORED_COMMAND 301s (process:2466): libfprint-device-DEBUG: 05:02:00.638: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.638: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.638: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.638: 78556461: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.638: Processing command ERROR 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.638: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.638: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.638: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s ok 301s test_open_error_with_keep_alive (__main__.VirtualDevice.test_open_error_with_keep_alive) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.638: 78556658: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.638: 78556671: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.638: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.638: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.638: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.638: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.638: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.638: Received command SET_KEEP_ALIVE 1 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.638: Keep alive toggled: 1 301s (process:2466): libfprint-device-DEBUG: 05:02:00.638: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.638: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.638: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.639: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.639: Got instructions of length 7 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.639: Received command ERROR 5 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.639: 78557363: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.639: Processing command ERROR 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.639: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.639: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.639: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s ok 301s test_quick_enroll (__main__.VirtualDevice.test_quick_enroll) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.639: 78557515: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-device-DEBUG: 05:02:00.639: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.639: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.639: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.639: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.639: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.639: Received command SET_ENROLL_STAGES 1 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.639: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.639: Got instructions of length 14 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.639: Received command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.639: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.639: Processing command SCAN testprint 301s (process:2466): libfprint-device-DEBUG: 05:02:00.639: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.639: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 301s (process:2466): libfprint-device-DEBUG: 05:02:00.639: Device reported finger status change: FP_FINGER_STATUS_NEEDED 301s (process:2466): libfprint-device-DEBUG: 05:02:00.639: Device reported enroll progress, reported 1 of 1 have been completed 301s (process:2466): libfprint-device-DEBUG: 05:02:00.639: Device reported enroll completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.639: Device reported finger status change: FP_FINGER_STATUS_NONE 301s (process:2466): libfprint-device-DEBUG: 05:02:00.639: Print for finger FP_FINGER_LEFT_LITTLE enrolled 301s (process:2466): libfprint-device-DEBUG: 05:02:00.640: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.640: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.640: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.640: Got instructions of length 16 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.640: Received command SET_KEEP_ALIVE 0 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.640: Keep alive toggled: 0 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.640: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.640: Got instructions of length 19 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.640: Received command SET_ENROLL_STAGES 5 301s (process:2466): libfprint-device-DEBUG: 05:02:00.640: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.640: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.640: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 301s Enroll done 301s ok 301s (process:2466): libfprint-context-DEBUG: 05:02:00.641: Initializing FpContext (libfprint version 1.94.9+tod1) 301s (process:2466): libfprint-tod-DEBUG: 05:02:00.641: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 301s (process:2466): libfprint-context-DEBUG: 05:02:00.643: No driver found for USB device 1D6B:0003 301s (process:2466): libfprint-context-DEBUG: 05:02:00.643: No driver found for USB device 0627:0001 301s (process:2466): libfprint-context-DEBUG: 05:02:00.643: No driver found for USB device 1D6B:0002 301s (process:2466): libfprint-context-DEBUG: 05:02:00.643: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-ia1mqlgh/virtual-device.socket 301s (process:2466): libfprint-context-DEBUG: 05:02:00.643: created 301s (process:2466): libfprint-device-DEBUG: 05:02:00.644: Device reported probe completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.644: Completing action FPI_DEVICE_ACTION_PROBE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.644: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 301s test_capture (__main__.VirtualDeviceBusyDeviceOperations.test_capture) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.644: 78562690: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.644: 78562712: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.644: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.644: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.644: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.644: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.644: Got instructions of length 9 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.644: Received command SLEEP 200 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.644: Processing command SLEEP 200 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.645: Sleeping 200ms 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.845: Sleeping completed 301s (process:2466): libfprint-device-DEBUG: 05:02:00.845: Device reported close completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.845: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.845: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 301s ok 301s test_close (__main__.VirtualDeviceBusyDeviceOperations.test_close) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.845: 78763897: ../libfprint/drivers/virtual-device.c:387 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.845: 78763916: ../libfprint/drivers/virtual-device-listener.c:153 301s (process:2466): libfprint-device-DEBUG: 05:02:00.846: Device reported open completion 301s (process:2466): libfprint-device-DEBUG: 05:02:00.846: Completing action FPI_DEVICE_ACTION_OPEN in idle! 301s (process:2466): libfprint-device-DEBUG: 05:02:00.846: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 301s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:00.846: Got a new connection! 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.846: Got instructions of length 9 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.846: Received command SLEEP 200 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.846: Processing command SLEEP 200 301s (process:2466): libfprint-virtual_device-DEBUG: 05:02:00.846: Sleeping 200ms 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.046: Sleeping completed 302s (process:2466): libfprint-device-DEBUG: 05:02:01.046: Device reported close completion 302s (process:2466): libfprint-device-DEBUG: 05:02:01.047: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 302s (process:2466): libfprint-device-DEBUG: 05:02:01.047: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 302s ok 302s test_delete_print (__main__.VirtualDeviceBusyDeviceOperations.test_delete_print) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.047: 78965411: ../libfprint/drivers/virtual-device.c:387 302s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:01.047: 78965426: ../libfprint/drivers/virtual-device-listener.c:153 302s (process:2466): libfprint-device-DEBUG: 05:02:01.047: Device reported open completion 302s (process:2466): libfprint-device-DEBUG: 05:02:01.047: Completing action FPI_DEVICE_ACTION_OPEN in idle! 302s (process:2466): libfprint-device-DEBUG: 05:02:01.047: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 302s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:01.048: Got a new connection! 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.048: Got instructions of length 9 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.048: Received command SLEEP 200 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.048: Processing command SLEEP 200 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.048: Sleeping 200ms 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.248: Sleeping completed 302s (process:2466): libfprint-device-DEBUG: 05:02:01.248: Device reported close completion 302s (process:2466): libfprint-device-DEBUG: 05:02:01.248: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 302s (process:2466): libfprint-device-DEBUG: 05:02:01.248: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 302s ok 302s test_enroll (__main__.VirtualDeviceBusyDeviceOperations.test_enroll) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.249: 79167229: ../libfprint/drivers/virtual-device.c:387 302s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:01.249: 79167246: ../libfprint/drivers/virtual-device-listener.c:153 302s (process:2466): libfprint-device-DEBUG: 05:02:01.249: Device reported open completion 302s (process:2466): libfprint-device-DEBUG: 05:02:01.249: Completing action FPI_DEVICE_ACTION_OPEN in idle! 302s (process:2466): libfprint-device-DEBUG: 05:02:01.249: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 302s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:01.249: Got a new connection! 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.249: Got instructions of length 9 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.249: Received command SLEEP 200 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.249: Processing command SLEEP 200 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.249: Sleeping 200ms 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.450: Sleeping completed 302s (process:2466): libfprint-device-DEBUG: 05:02:01.450: Device reported close completion 302s (process:2466): libfprint-device-DEBUG: 05:02:01.450: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 302s (process:2466): libfprint-device-DEBUG: 05:02:01.450: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 302s ok 302s test_identify (__main__.VirtualDeviceBusyDeviceOperations.test_identify) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.450: 79368615: ../libfprint/drivers/virtual-device.c:387 302s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:01.450: 79368625: ../libfprint/drivers/virtual-device-listener.c:153 302s (process:2466): libfprint-device-DEBUG: 05:02:01.450: Device reported open completion 302s (process:2466): libfprint-device-DEBUG: 05:02:01.450: Completing action FPI_DEVICE_ACTION_OPEN in idle! 302s (process:2466): libfprint-device-DEBUG: 05:02:01.450: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 302s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:01.451: Got a new connection! 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.451: Got instructions of length 9 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.451: Received command SLEEP 200 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.451: Processing command SLEEP 200 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.451: Sleeping 200ms 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.651: Sleeping completed 302s (process:2466): libfprint-device-DEBUG: 05:02:01.651: Device reported close completion 302s (process:2466): libfprint-device-DEBUG: 05:02:01.651: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 302s (process:2466): libfprint-device-DEBUG: 05:02:01.652: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 302s ok 302s test_list_prints (__main__.VirtualDeviceBusyDeviceOperations.test_list_prints) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.652: 79570349: ../libfprint/drivers/virtual-device.c:387 302s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:01.652: 79570371: ../libfprint/drivers/virtual-device-listener.c:153 302s (process:2466): libfprint-device-DEBUG: 05:02:01.652: Device reported open completion 302s (process:2466): libfprint-device-DEBUG: 05:02:01.652: Completing action FPI_DEVICE_ACTION_OPEN in idle! 302s (process:2466): libfprint-device-DEBUG: 05:02:01.652: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 302s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:01.652: Got a new connection! 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.653: Got instructions of length 9 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.653: Received command SLEEP 200 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.653: Processing command SLEEP 200 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.653: Sleeping 200ms 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.853: Sleeping completed 302s (process:2466): libfprint-device-DEBUG: 05:02:01.853: Device reported close completion 302s (process:2466): libfprint-device-DEBUG: 05:02:01.853: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 302s (process:2466): libfprint-device-DEBUG: 05:02:01.853: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 302s ok 302s test_open (__main__.VirtualDeviceBusyDeviceOperations.test_open) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.854: 79772226: ../libfprint/drivers/virtual-device.c:387 302s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:01.854: 79772244: ../libfprint/drivers/virtual-device-listener.c:153 302s (process:2466): libfprint-device-DEBUG: 05:02:01.854: Device reported open completion 302s (process:2466): libfprint-device-DEBUG: 05:02:01.854: Completing action FPI_DEVICE_ACTION_OPEN in idle! 302s (process:2466): libfprint-device-DEBUG: 05:02:01.854: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 302s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:01.854: Got a new connection! 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.854: Got instructions of length 9 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.854: Received command SLEEP 200 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.855: Processing command SLEEP 200 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.855: Sleeping 200ms 302s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:01.855: Got a new connection! 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.855: Got instructions of length 16 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.855: Received command SET_KEEP_ALIVE 1 302s (process:2466): libfprint-virtual_device-DEBUG: 05:02:01.855: Keep alive toggled: 1 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.055: Sleeping completed 303s (process:2466): libfprint-device-DEBUG: 05:02:02.055: Device reported close completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.055: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.055: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.055: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.056: Got instructions of length 9 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.056: Received command SLEEP 100 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.056: 79974263: ../libfprint/drivers/virtual-device.c:387 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.056: Processing command SLEEP 100 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.056: Sleeping 100ms 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.156: Sleeping completed 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.156: 80074530: ../libfprint/drivers/virtual-device.c:387 303s (process:2466): libfprint-device-DEBUG: 05:02:02.156: Device reported open completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.156: Completing action FPI_DEVICE_ACTION_OPEN in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.156: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-device-DEBUG: 05:02:02.156: Device reported close completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.156: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.156: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s ok 303s test_verify (__main__.VirtualDeviceBusyDeviceOperations.test_verify) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.156: 80074876: ../libfprint/drivers/virtual-device.c:387 303s (process:2466): libfprint-device-DEBUG: 05:02:02.156: Device reported open completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.156: Completing action FPI_DEVICE_ACTION_OPEN in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.156: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.157: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.157: Got instructions of length 9 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.157: Received command SLEEP 200 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.157: Processing command SLEEP 200 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.157: Sleeping 200ms 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.357: Sleeping completed 303s (process:2466): libfprint-device-DEBUG: 05:02:02.357: Device reported close completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.357: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.357: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s ok 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.358: 80276193: ../libfprint/drivers/virtual-device.c:752 303s (process:2466): libfprint-context-DEBUG: 05:02:02.358: Initializing FpContext (libfprint version 1.94.9+tod1) 303s (process:2466): libfprint-tod-DEBUG: 05:02:02.358: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 303s (process:2466): libfprint-context-DEBUG: 05:02:02.361: No driver found for USB device 1D6B:0003 303s (process:2466): libfprint-context-DEBUG: 05:02:02.361: No driver found for USB device 0627:0001 303s (process:2466): libfprint-context-DEBUG: 05:02:02.361: No driver found for USB device 1D6B:0002 303s (process:2466): libfprint-context-DEBUG: 05:02:02.361: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-qtc26p_n/virtual-device.socket 303s (process:2466): libfprint-context-DEBUG: 05:02:02.361: created 303s (process:2466): libfprint-device-DEBUG: 05:02:02.362: Device reported probe completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.362: Completing action FPI_DEVICE_ACTION_PROBE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.362: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s test_capture (__main__.VirtualDeviceClosed.test_capture) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.362: 80280536: ../libfprint/drivers/virtual-device.c:387 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.362: 80280556: ../libfprint/drivers/virtual-device-listener.c:153 303s (process:2466): libfprint-device-DEBUG: 05:02:02.362: Device reported open completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.362: Completing action FPI_DEVICE_ACTION_OPEN in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.362: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-device-DEBUG: 05:02:02.362: Device reported close completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.362: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.362: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s ok 303s test_close (__main__.VirtualDeviceClosed.test_close) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.363: 80281196: ../libfprint/drivers/virtual-device.c:387 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.363: 80281226: ../libfprint/drivers/virtual-device-listener.c:153 303s (process:2466): libfprint-device-DEBUG: 05:02:02.363: Device reported open completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.363: Completing action FPI_DEVICE_ACTION_OPEN in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.363: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-device-DEBUG: 05:02:02.363: Device reported close completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.363: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.363: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s ok 303s test_delete_print (__main__.VirtualDeviceClosed.test_delete_print) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.363: 80281754: ../libfprint/drivers/virtual-device.c:387 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.363: 80281805: ../libfprint/drivers/virtual-device-listener.c:153 303s (process:2466): libfprint-device-DEBUG: 05:02:02.363: Device reported open completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.363: Completing action FPI_DEVICE_ACTION_OPEN in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.363: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-device-DEBUG: 05:02:02.363: Device reported close completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.363: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.364: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s ok 303s test_enroll (__main__.VirtualDeviceClosed.test_enroll) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.364: 80282431: ../libfprint/drivers/virtual-device.c:387 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.364: 80282462: ../libfprint/drivers/virtual-device-listener.c:153 303s (process:2466): libfprint-device-DEBUG: 05:02:02.364: Device reported open completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.364: Completing action FPI_DEVICE_ACTION_OPEN in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.364: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-device-DEBUG: 05:02:02.364: Device reported close completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.364: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.364: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s ok 303s test_identify (__main__.VirtualDeviceClosed.test_identify) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.365: 80283162: ../libfprint/drivers/virtual-device.c:387 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.365: 80283197: ../libfprint/drivers/virtual-device-listener.c:153 303s (process:2466): libfprint-device-DEBUG: 05:02:02.365: Device reported open completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.365: Completing action FPI_DEVICE_ACTION_OPEN in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.365: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-device-DEBUG: 05:02:02.365: Device reported close completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.365: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.365: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s ok 303s test_list_prints (__main__.VirtualDeviceClosed.test_list_prints) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.365: 80283695: ../libfprint/drivers/virtual-device.c:387 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.365: 80283730: ../libfprint/drivers/virtual-device-listener.c:153 303s (process:2466): libfprint-device-DEBUG: 05:02:02.365: Device reported open completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.365: Completing action FPI_DEVICE_ACTION_OPEN in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.365: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-device-DEBUG: 05:02:02.365: Device reported close completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.365: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.365: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s ok 303s test_verify (__main__.VirtualDeviceClosed.test_verify) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.366: 80284240: ../libfprint/drivers/virtual-device.c:387 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.366: 80284272: ../libfprint/drivers/virtual-device-listener.c:153 303s (process:2466): libfprint-device-DEBUG: 05:02:02.366: Device reported open completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.366: Completing action FPI_DEVICE_ACTION_OPEN in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.366: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-device-DEBUG: 05:02:02.366: Device reported close completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.366: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.366: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s ok 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.366: 80285128: ../libfprint/drivers/virtual-device.c:752 303s (process:2466): libfprint-context-DEBUG: 05:02:02.367: Initializing FpContext (libfprint version 1.94.9+tod1) 303s (process:2466): libfprint-tod-DEBUG: 05:02:02.367: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 303s (process:2466): libfprint-context-DEBUG: 05:02:02.369: No driver found for USB device 1D6B:0003 303s (process:2466): libfprint-context-DEBUG: 05:02:02.370: No driver found for USB device 0627:0001 303s (process:2466): libfprint-context-DEBUG: 05:02:02.370: No driver found for USB device 1D6B:0002 303s (process:2466): libfprint-context-DEBUG: 05:02:02.370: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-qtc26p_n/virtual-device.socket 303s (process:2466): libfprint-context-DEBUG: 05:02:02.370: created 303s (process:2466): libfprint-context-DEBUG: 05:02:02.370: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-u8jqzv12/virtual-device-storage.socket 303s (process:2466): libfprint-context-DEBUG: 05:02:02.370: created 303s (process:2466): libfprint-device-DEBUG: 05:02:02.371: Device reported probe completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.371: Device reported probe completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.371: Completing action FPI_DEVICE_ACTION_PROBE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.371: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-device-DEBUG: 05:02:02.371: Completing action FPI_DEVICE_ACTION_PROBE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.371: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s test_capture_unsupported (__main__.VirtualDeviceStorage.test_capture_unsupported) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.371: 80289744: ../libfprint/drivers/virtual-device.c:387 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.371: 80289820: ../libfprint/drivers/virtual-device-listener.c:153 303s (process:2466): libfprint-device-DEBUG: 05:02:02.371: Device reported open completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.371: Completing action FPI_DEVICE_ACTION_OPEN in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.371: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.372: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.372: Got instructions of length 5 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.372: Received command CONT 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.372: Processing command CONT 303s (process:2466): libfprint-device-DEBUG: 05:02:02.372: Device reported deletion completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.372: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.372: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.372: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.372: Got instructions of length 16 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.372: Received command SET_KEEP_ALIVE 0 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.372: Keep alive toggled: 0 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.372: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.372: Got instructions of length 19 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.372: Received command SET_ENROLL_STAGES 5 303s (process:2466): libfprint-device-DEBUG: 05:02:02.372: Device reported close completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.372: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.372: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s ok 303s test_change_enroll_stages (__main__.VirtualDeviceStorage.test_change_enroll_stages) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.372: 80291117: ../libfprint/drivers/virtual-device.c:387 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.372: 80291128: ../libfprint/drivers/virtual-device-listener.c:153 303s (process:2466): libfprint-device-DEBUG: 05:02:02.373: Device reported open completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.373: Completing action FPI_DEVICE_ACTION_OPEN in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.373: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.373: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.373: Got instructions of length 20 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.373: Received command SET_ENROLL_STAGES 20 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.373: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.373: Got instructions of length 19 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.373: Received command SET_ENROLL_STAGES 1 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.374: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.374: Got instructions of length 19 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.374: Received command SET_ENROLL_STAGES 0 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.374: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.374: Got instructions of length 5 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.374: Received command CONT 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.374: Processing command CONT 303s (process:2466): libfprint-device-DEBUG: 05:02:02.374: Device reported deletion completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.374: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.374: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.374: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.374: Got instructions of length 16 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.375: Received command SET_KEEP_ALIVE 0 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.375: Keep alive toggled: 0 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.375: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.375: Got instructions of length 19 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.375: Received command SET_ENROLL_STAGES 5 303s (process:2466): libfprint-device-DEBUG: 05:02:02.375: Device reported close completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.375: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.375: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s ok 303s test_change_scan_type (__main__.VirtualDeviceStorage.test_change_scan_type) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.375: 80293695: ../libfprint/drivers/virtual-device.c:387 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.375: 80293723: ../libfprint/drivers/virtual-device-listener.c:153 303s (process:2466): libfprint-device-DEBUG: 05:02:02.375: Device reported open completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.375: Completing action FPI_DEVICE_ACTION_OPEN in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.375: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.376: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.376: Got instructions of length 19 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.376: Received command SET_SCAN_TYPE press 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.376: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.376: Got instructions of length 19 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.376: Received command SET_SCAN_TYPE swipe 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.376: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.376: Got instructions of length 25 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.376: Received command SET_SCAN_TYPE eye-contact 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.377: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.377: Got instructions of length 5 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.377: Received command CONT 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.377: Processing command CONT 303s (process:2466): libfprint-device-DEBUG: 05:02:02.377: Device reported deletion completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.377: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.377: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.377: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.377: Got instructions of length 16 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.377: Received command SET_KEEP_ALIVE 0 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.377: Keep alive toggled: 0 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.377: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.377: Got instructions of length 19 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.377: Received command SET_ENROLL_STAGES 5 303s (process:2466): libfprint-device-DEBUG: 05:02:02.377: Device reported close completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.378: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.378: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s ok 303s test_clear_storage (__main__.VirtualDeviceStorage.test_clear_storage) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.378: 80296394: ../libfprint/drivers/virtual-device.c:387 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.378: 80296418: ../libfprint/drivers/virtual-device-listener.c:153 303s (process:2466): libfprint-device-DEBUG: 05:02:02.378: Device reported open completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.378: Completing action FPI_DEVICE_ACTION_OPEN in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.378: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.378: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.378: Got instructions of length 9 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.378: Received command INSERT p1 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.378: Processing command INSERT p1 303s (process:2466): libfprint-device-DEBUG: 05:02:02.879: Device reported listing completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.879: Completing action FPI_DEVICE_ACTION_LIST in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.879: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 303s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:02.879: Got a new connection! 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.879: Got instructions of length 5 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.879: Received command CONT 303s (process:2466): libfprint-virtual_device-DEBUG: 05:02:02.880: Processing command CONT 303s (process:2466): libfprint-device-DEBUG: 05:02:02.880: Device reported deletion completion 303s (process:2466): libfprint-device-DEBUG: 05:02:02.880: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 303s (process:2466): libfprint-device-DEBUG: 05:02:02.880: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 304s (process:2466): libfprint-device-DEBUG: 05:02:03.380: Device reported listing completion 304s (process:2466): libfprint-device-DEBUG: 05:02:03.380: Completing action FPI_DEVICE_ACTION_LIST in idle! 304s (process:2466): libfprint-device-DEBUG: 05:02:03.380: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 304s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:03.381: Got a new connection! 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.381: Got instructions of length 5 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.381: Received command CONT 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.381: Processing command CONT 304s (process:2466): libfprint-device-DEBUG: 05:02:03.381: Device reported deletion completion 304s (process:2466): libfprint-device-DEBUG: 05:02:03.381: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 304s (process:2466): libfprint-device-DEBUG: 05:02:03.381: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 304s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:03.381: Got a new connection! 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.381: Got instructions of length 16 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.381: Received command SET_KEEP_ALIVE 0 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.381: Keep alive toggled: 0 304s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:03.381: Got a new connection! 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.382: Got instructions of length 19 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.382: Received command SET_ENROLL_STAGES 5 304s (process:2466): libfprint-device-DEBUG: 05:02:03.382: Device reported close completion 304s (process:2466): libfprint-device-DEBUG: 05:02:03.382: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 304s (process:2466): libfprint-device-DEBUG: 05:02:03.382: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 304s 304s ok 304s test_clear_storage_error (__main__.VirtualDeviceStorage.test_clear_storage_error) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.382: 81300588: ../libfprint/drivers/virtual-device.c:387 304s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:03.382: 81300614: ../libfprint/drivers/virtual-device-listener.c:153 304s (process:2466): libfprint-device-DEBUG: 05:02:03.382: Device reported open completion 304s (process:2466): libfprint-device-DEBUG: 05:02:03.382: Completing action FPI_DEVICE_ACTION_OPEN in idle! 304s (process:2466): libfprint-device-DEBUG: 05:02:03.382: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 304s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:03.382: Got a new connection! 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.383: Got instructions of length 9 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.383: Received command INSERT p1 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.383: Processing command INSERT p1 304s (process:2466): libfprint-device-DEBUG: 05:02:03.883: Device reported listing completion 304s (process:2466): libfprint-device-DEBUG: 05:02:03.883: Completing action FPI_DEVICE_ACTION_LIST in idle! 304s (process:2466): libfprint-device-DEBUG: 05:02:03.883: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 304s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:03.884: Got a new connection! 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.884: Got instructions of length 7 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.884: Received command ERROR 5 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.884: Processing command ERROR 5 304s (process:2466): libfprint-device-DEBUG: 05:02:03.884: Device reported deletion completion 304s (process:2466): libfprint-device-DEBUG: 05:02:03.884: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 304s (process:2466): libfprint-device-DEBUG: 05:02:03.884: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 304s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:03.884: Got a new connection! 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.885: Got instructions of length 5 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.885: Received command CONT 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.885: Processing command CONT 304s (process:2466): libfprint-device-DEBUG: 05:02:03.885: Device reported deletion completion 304s (process:2466): libfprint-device-DEBUG: 05:02:03.885: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 304s (process:2466): libfprint-device-DEBUG: 05:02:03.885: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 304s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:03.885: Got a new connection! 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.885: Got instructions of length 16 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.885: Received command SET_KEEP_ALIVE 0 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.885: Keep alive toggled: 0 304s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:03.885: Got a new connection! 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.885: Got instructions of length 19 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.885: Received command SET_ENROLL_STAGES 5 304s (process:2466): libfprint-device-DEBUG: 05:02:03.885: Device reported close completion 304s (process:2466): libfprint-device-DEBUG: 05:02:03.885: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 304s (process:2466): libfprint-device-DEBUG: 05:02:03.886: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 304s 304s ok 304s test_close_error (__main__.VirtualDeviceStorage.test_close_error) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.886: 81804468: ../libfprint/drivers/virtual-device.c:387 304s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:03.886: 81804483: ../libfprint/drivers/virtual-device-listener.c:153 304s (process:2466): libfprint-device-DEBUG: 05:02:03.886: Device reported open completion 304s (process:2466): libfprint-device-DEBUG: 05:02:03.886: Completing action FPI_DEVICE_ACTION_OPEN in idle! 304s (process:2466): libfprint-device-DEBUG: 05:02:03.886: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 304s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:03.886: Got a new connection! 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.886: Got instructions of length 9 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.886: Received command SLEEP 100 304s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:03.886: Got a new connection! 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.886: Got instructions of length 7 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.886: Received command ERROR 4 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.886: Processing command SLEEP 100 304s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.886: Sleeping 100ms 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.987: Sleeping completed 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.987: Processing command ERROR 4 305s (process:2466): libfprint-device-DEBUG: 05:02:03.987: Device reported close completion 305s (process:2466): libfprint-device-DEBUG: 05:02:03.987: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 305s (process:2466): libfprint-device-DEBUG: 05:02:03.987: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s ok 305s test_close_while_opening (__main__.VirtualDeviceStorage.test_close_while_opening) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.987: 81905947: ../libfprint/drivers/virtual-device.c:387 305s (process:2466): libfprint-device-DEBUG: 05:02:03.987: Device reported open completion 305s (process:2466): libfprint-device-DEBUG: 05:02:03.987: Completing action FPI_DEVICE_ACTION_OPEN in idle! 305s (process:2466): libfprint-device-DEBUG: 05:02:03.987: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:03.988: Got a new connection! 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.988: Got instructions of length 16 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.988: Received command SET_KEEP_ALIVE 1 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.988: Keep alive toggled: 1 305s (process:2466): libfprint-device-DEBUG: 05:02:03.988: Device reported close completion 305s (process:2466): libfprint-device-DEBUG: 05:02:03.988: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 305s (process:2466): libfprint-device-DEBUG: 05:02:03.988: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:03.988: Got a new connection! 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.988: Got instructions of length 9 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.988: Received command SLEEP 500 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.988: 81906701: ../libfprint/drivers/virtual-device.c:387 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.988: Processing command SLEEP 500 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:03.988: Sleeping 500ms 305s Executing: libfprint-2/virtual-device.test 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.489: Sleeping completed 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.489: 82407814: ../libfprint/drivers/virtual-device.c:387 305s (process:2466): libfprint-device-DEBUG: 05:02:04.489: Device reported open completion 305s (process:2466): libfprint-device-DEBUG: 05:02:04.489: Completing action FPI_DEVICE_ACTION_OPEN in idle! 305s (process:2466): libfprint-device-DEBUG: 05:02:04.489: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:04.490: Got a new connection! 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.490: Got instructions of length 5 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.490: Received command CONT 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.490: Processing command CONT 305s (process:2466): libfprint-device-DEBUG: 05:02:04.490: Device reported deletion completion 305s (process:2466): libfprint-device-DEBUG: 05:02:04.490: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 305s (process:2466): libfprint-device-DEBUG: 05:02:04.490: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:04.490: Got a new connection! 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.490: Got instructions of length 16 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.490: Received command SET_KEEP_ALIVE 0 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.490: Keep alive toggled: 0 305s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:04.490: Got a new connection! 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.490: Got instructions of length 19 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.490: Received command SET_ENROLL_STAGES 5 305s (process:2466): libfprint-device-DEBUG: 05:02:04.490: Device reported close completion 305s (process:2466): libfprint-device-DEBUG: 05:02:04.491: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 305s (process:2466): libfprint-device-DEBUG: 05:02:04.491: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s ok 305s test_delayed_open (__main__.VirtualDeviceStorage.test_delayed_open) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.491: 82409615: ../libfprint/drivers/virtual-device.c:387 305s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:04.491: 82409675: ../libfprint/drivers/virtual-device-listener.c:153 305s (process:2466): libfprint-device-DEBUG: 05:02:04.491: Device reported open completion 305s (process:2466): libfprint-device-DEBUG: 05:02:04.491: Completing action FPI_DEVICE_ACTION_OPEN in idle! 305s (process:2466): libfprint-device-DEBUG: 05:02:04.491: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:04.492: Got a new connection! 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.492: Got instructions of length 16 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.492: Received command IGNORED_COMMAND 305s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:04.492: Got a new connection! 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.492: Got instructions of length 9 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.492: Received command SLEEP 500 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.492: Processing command IGNORED_COMMAND 305s (process:2466): libfprint-device-DEBUG: 05:02:04.492: Device reported close completion 305s (process:2466): libfprint-device-DEBUG: 05:02:04.492: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 305s (process:2466): libfprint-device-DEBUG: 05:02:04.492: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.492: 82410923: ../libfprint/drivers/virtual-device.c:387 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.492: Processing command SLEEP 500 305s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.492: Sleeping 500ms 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.993: Sleeping completed 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.993: 82911674: ../libfprint/drivers/virtual-device.c:387 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:04.993: 82911702: ../libfprint/drivers/virtual-device-listener.c:153 306s (process:2466): libfprint-device-DEBUG: 05:02:04.993: Device reported open completion 306s (process:2466): libfprint-device-DEBUG: 05:02:04.993: Completing action FPI_DEVICE_ACTION_OPEN in idle! 306s (process:2466): libfprint-device-DEBUG: 05:02:04.994: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:04.994: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.994: Got instructions of length 5 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.994: Received command CONT 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.994: Processing command CONT 306s (process:2466): libfprint-device-DEBUG: 05:02:04.995: Device reported deletion completion 306s (process:2466): libfprint-device-DEBUG: 05:02:04.995: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 306s (process:2466): libfprint-device-DEBUG: 05:02:04.995: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:04.995: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.995: Got instructions of length 16 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.995: Received command SET_KEEP_ALIVE 0 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.995: Keep alive toggled: 0 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:04.995: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.996: Got instructions of length 19 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.996: Received command SET_ENROLL_STAGES 5 306s (process:2466): libfprint-device-DEBUG: 05:02:04.996: Device reported close completion 306s (process:2466): libfprint-device-DEBUG: 05:02:04.996: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 306s (process:2466): libfprint-device-DEBUG: 05:02:04.996: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s ok 306s test_delayed_open_with_keep_alive (__main__.VirtualDeviceStorage.test_delayed_open_with_keep_alive) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.996: 82914809: ../libfprint/drivers/virtual-device.c:387 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:04.996: 82914850: ../libfprint/drivers/virtual-device-listener.c:153 306s (process:2466): libfprint-device-DEBUG: 05:02:04.996: Device reported open completion 306s (process:2466): libfprint-device-DEBUG: 05:02:04.996: Completing action FPI_DEVICE_ACTION_OPEN in idle! 306s (process:2466): libfprint-device-DEBUG: 05:02:04.997: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:04.997: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.997: Got instructions of length 16 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.997: Received command SET_KEEP_ALIVE 1 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.997: Keep alive toggled: 1 306s (process:2466): libfprint-device-DEBUG: 05:02:04.997: Device reported close completion 306s (process:2466): libfprint-device-DEBUG: 05:02:04.997: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 306s (process:2466): libfprint-device-DEBUG: 05:02:04.997: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:04.997: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.998: Got instructions of length 9 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.998: Received command SLEEP 500 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.998: 82916315: ../libfprint/drivers/virtual-device.c:387 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.998: Processing command SLEEP 500 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:04.998: Sleeping 500ms 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.498: Sleeping completed 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.498: 83417117: ../libfprint/drivers/virtual-device.c:387 306s (process:2466): libfprint-device-DEBUG: 05:02:05.498: Device reported open completion 306s (process:2466): libfprint-device-DEBUG: 05:02:05.499: Completing action FPI_DEVICE_ACTION_OPEN in idle! 306s (process:2466): libfprint-device-DEBUG: 05:02:05.499: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.499: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.499: Got instructions of length 5 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.499: Received command CONT 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.499: Processing command CONT 306s (process:2466): libfprint-device-DEBUG: 05:02:05.500: Device reported deletion completion 306s (process:2466): libfprint-device-DEBUG: 05:02:05.500: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 306s (process:2466): libfprint-device-DEBUG: 05:02:05.500: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.500: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.500: Got instructions of length 16 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.500: Received command SET_KEEP_ALIVE 0 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.500: Keep alive toggled: 0 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.500: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.500: Got instructions of length 19 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.500: Received command SET_ENROLL_STAGES 5 306s (process:2466): libfprint-device-DEBUG: 05:02:05.500: Device reported close completion 306s (process:2466): libfprint-device-DEBUG: 05:02:05.500: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 306s (process:2466): libfprint-device-DEBUG: 05:02:05.500: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s ok 306s test_delete_error (__main__.VirtualDeviceStorage.test_delete_error) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.500: 83418890: ../libfprint/drivers/virtual-device.c:387 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.500: 83418901: ../libfprint/drivers/virtual-device-listener.c:153 306s (process:2466): libfprint-device-DEBUG: 05:02:05.501: Device reported open completion 306s (process:2466): libfprint-device-DEBUG: 05:02:05.501: Completing action FPI_DEVICE_ACTION_OPEN in idle! 306s (process:2466): libfprint-device-DEBUG: 05:02:05.501: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.501: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.501: Got instructions of length 9 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.501: Received command SLEEP 100 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.502: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.502: Got instructions of length 7 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.502: Received command ERROR 7 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.502: Processing command SLEEP 100 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.502: Sleeping 100ms 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.602: Sleeping completed 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.602: Processing command ERROR 7 306s (process:2466): libfprint-device-DEBUG: 05:02:05.603: Device reported deletion completion 306s (process:2466): libfprint-device-DEBUG: 05:02:05.603: Completing action FPI_DEVICE_ACTION_DELETE in idle! 306s (process:2466): libfprint-device-DEBUG: 05:02:05.603: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.603: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.603: Got instructions of length 5 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.603: Received command CONT 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.604: Processing command CONT 306s (process:2466): libfprint-device-DEBUG: 05:02:05.604: Device reported deletion completion 306s (process:2466): libfprint-device-DEBUG: 05:02:05.604: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 306s (process:2466): libfprint-device-DEBUG: 05:02:05.604: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.604: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.604: Got instructions of length 16 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.604: Received command SET_KEEP_ALIVE 0 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.604: Keep alive toggled: 0 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.604: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.605: Got instructions of length 19 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.605: Received command SET_ENROLL_STAGES 5 306s (process:2466): libfprint-device-DEBUG: 05:02:05.605: Device reported close completion 306s (process:2466): libfprint-device-DEBUG: 05:02:05.605: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 306s (process:2466): libfprint-device-DEBUG: 05:02:05.605: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s ok 306s test_delete_multiple_times (__main__.VirtualDeviceStorage.test_delete_multiple_times) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.605: 83523616: ../libfprint/drivers/virtual-device.c:387 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.605: 83523629: ../libfprint/drivers/virtual-device-listener.c:153 306s (process:2466): libfprint-device-DEBUG: 05:02:05.605: Device reported open completion 306s (process:2466): libfprint-device-DEBUG: 05:02:05.605: Completing action FPI_DEVICE_ACTION_OPEN in idle! 306s (process:2466): libfprint-device-DEBUG: 05:02:05.605: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.605: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.605: Got instructions of length 16 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.605: Received command SCAN right-thumb 306s (process:2466): libfprint-device-DEBUG: 05:02:05.605: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.606: Processing command SCAN right-thumb 306s (process:2466): libfprint-device-DEBUG: 05:02:05.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED 306s (process:2466): libfprint-device-DEBUG: 05:02:05.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 306s (process:2466): libfprint-device-DEBUG: 05:02:05.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED 306s (process:2466): libfprint-device-DEBUG: 05:02:05.606: Device reported enroll progress, reported 1 of 5 have been completed 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.606: Sleeping completed 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.606: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.606: Got instructions of length 16 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.606: Received command SCAN right-thumb 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.606: Processing command SCAN right-thumb 306s (process:2466): libfprint-device-DEBUG: 05:02:05.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 306s (process:2466): libfprint-device-DEBUG: 05:02:05.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED 306s (process:2466): libfprint-device-DEBUG: 05:02:05.606: Device reported enroll progress, reported 2 of 5 have been completed 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.606: Sleeping completed 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.606: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.606: Got instructions of length 16 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.606: Received command SCAN right-thumb 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.606: Processing command SCAN right-thumb 306s (process:2466): libfprint-device-DEBUG: 05:02:05.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 306s (process:2466): libfprint-device-DEBUG: 05:02:05.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED 306s (process:2466): libfprint-device-DEBUG: 05:02:05.606: Device reported enroll progress, reported 3 of 5 have been completed 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.606: Sleeping completed 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.606: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.606: Got instructions of length 16 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.606: Received command SCAN right-thumb 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.606: Processing command SCAN right-thumb 306s (process:2466): libfprint-device-DEBUG: 05:02:05.607: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 306s (process:2466): libfprint-device-DEBUG: 05:02:05.607: Device reported finger status change: FP_FINGER_STATUS_NEEDED 306s (process:2466): libfprint-device-DEBUG: 05:02:05.607: Device reported enroll progress, reported 4 of 5 have been completed 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.607: Sleeping completed 306s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:05.607: Got a new connection! 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.607: Got instructions of length 16 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.607: Received command SCAN right-thumb 306s (process:2466): libfprint-virtual_device-DEBUG: 05:02:05.607: Processing command SCAN right-thumb 306s (process:2466): libfprint-device-DEBUG: 05:02:05.607: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 306s (process:2466): libfprint-device-DEBUG: 05:02:05.607: Device reported finger status change: FP_FINGER_STATUS_NEEDED 306s (process:2466): libfprint-device-DEBUG: 05:02:05.607: Device reported enroll progress, reported 5 of 5 have been completed 306s (process:2466): libfprint-device-DEBUG: 05:02:05.607: Device reported enroll completion 306s (process:2466): libfprint-device-DEBUG: 05:02:05.607: Device reported finger status change: FP_FINGER_STATUS_NONE 306s (process:2466): libfprint-device-DEBUG: 05:02:05.607: Print for finger FP_FINGER_RIGHT_THUMB enrolled 306s (process:2466): libfprint-device-DEBUG: 05:02:05.608: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 306s (process:2466): libfprint-device-DEBUG: 05:02:05.608: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:06.108: Deleting print right-thumb for user testuser 307s (process:2466): libfprint-device-DEBUG: 05:02:06.109: Device reported deletion completion 307s (process:2466): libfprint-device-DEBUG: 05:02:06.109: Completing action FPI_DEVICE_ACTION_DELETE in idle! 307s (process:2466): libfprint-device-DEBUG: 05:02:06.109: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:06.609: Deleting print right-thumb for user testuser 307s (process:2466): libfprint-device-DEBUG: 05:02:06.609: Device reported deletion completion 307s (process:2466): libfprint-device-DEBUG: 05:02:06.609: Completing action FPI_DEVICE_ACTION_DELETE in idle! 307s (process:2466): libfprint-device-DEBUG: 05:02:06.609: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:06.610: Got a new connection! 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.610: Got instructions of length 5 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.610: Received command CONT 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.610: Processing command CONT 307s (process:2466): libfprint-device-DEBUG: 05:02:06.610: Device reported deletion completion 307s (process:2466): libfprint-device-DEBUG: 05:02:06.610: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 307s (process:2466): libfprint-device-DEBUG: 05:02:06.610: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:06.611: Got a new connection! 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.611: Got instructions of length 16 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.611: Received command SET_KEEP_ALIVE 0 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.611: Keep alive toggled: 0 307s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:06.611: Got a new connection! 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.611: Got instructions of length 19 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.611: Received command SET_ENROLL_STAGES 5 307s (process:2466): libfprint-device-DEBUG: 05:02:06.612: Device reported close completion 307s (process:2466): libfprint-device-DEBUG: 05:02:06.612: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 307s (process:2466): libfprint-device-DEBUG: 05:02:06.612: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s Enroll done 307s ok 307s test_device_features (__main__.VirtualDeviceStorage.test_device_features) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.612: 84530547: ../libfprint/drivers/virtual-device.c:387 307s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:06.612: 84530590: ../libfprint/drivers/virtual-device-listener.c:153 307s (process:2466): libfprint-device-DEBUG: 05:02:06.612: Device reported open completion 307s (process:2466): libfprint-device-DEBUG: 05:02:06.612: Completing action FPI_DEVICE_ACTION_OPEN in idle! 307s (process:2466): libfprint-device-DEBUG: 05:02:06.612: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:06.613: Got a new connection! 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.613: Got instructions of length 5 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.613: Received command CONT 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.613: Processing command CONT 307s (process:2466): libfprint-device-DEBUG: 05:02:06.613: Device reported deletion completion 307s (process:2466): libfprint-device-DEBUG: 05:02:06.613: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 307s (process:2466): libfprint-device-DEBUG: 05:02:06.613: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:06.613: Got a new connection! 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.613: Got instructions of length 16 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.613: Received command SET_KEEP_ALIVE 0 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.613: Keep alive toggled: 0 307s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:06.614: Got a new connection! 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.614: Got instructions of length 19 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.614: Received command SET_ENROLL_STAGES 5 307s (process:2466): libfprint-device-DEBUG: 05:02:06.614: Device reported close completion 307s (process:2466): libfprint-device-DEBUG: 05:02:06.614: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 307s (process:2466): libfprint-device-DEBUG: 05:02:06.614: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s ok 307s test_device_properties (__main__.VirtualDeviceStorage.test_device_properties) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.614: 84532762: ../libfprint/drivers/virtual-device.c:387 307s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:06.614: 84532803: ../libfprint/drivers/virtual-device-listener.c:153 307s (process:2466): libfprint-device-DEBUG: 05:02:06.614: Device reported open completion 307s (process:2466): libfprint-device-DEBUG: 05:02:06.614: Completing action FPI_DEVICE_ACTION_OPEN in idle! 307s (process:2466): libfprint-device-DEBUG: 05:02:06.614: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:06.615: Got a new connection! 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.615: Got instructions of length 5 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.615: Received command CONT 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.615: Processing command CONT 307s (process:2466): libfprint-device-DEBUG: 05:02:06.615: Device reported deletion completion 307s (process:2466): libfprint-device-DEBUG: 05:02:06.615: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 307s (process:2466): libfprint-device-DEBUG: 05:02:06.615: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:06.615: Got a new connection! 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.615: Got instructions of length 16 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.615: Received command SET_KEEP_ALIVE 0 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.615: Keep alive toggled: 0 307s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:06.615: Got a new connection! 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.615: Got instructions of length 19 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.615: Received command SET_ENROLL_STAGES 5 307s (process:2466): libfprint-device-DEBUG: 05:02:06.616: Device reported close completion 307s (process:2466): libfprint-device-DEBUG: 05:02:06.616: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 307s (process:2466): libfprint-device-DEBUG: 05:02:06.616: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s ok 307s test_device_sleep (__main__.VirtualDeviceStorage.test_device_sleep) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.616: 84534547: ../libfprint/drivers/virtual-device.c:387 307s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:06.616: 84534584: ../libfprint/drivers/virtual-device-listener.c:153 307s (process:2466): libfprint-device-DEBUG: 05:02:06.616: Device reported open completion 307s (process:2466): libfprint-device-DEBUG: 05:02:06.616: Completing action FPI_DEVICE_ACTION_OPEN in idle! 307s (process:2466): libfprint-device-DEBUG: 05:02:06.616: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:06.616: Got a new connection! 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.616: Got instructions of length 10 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.616: Received command SLEEP 1500 307s (process:2466): libfprint-device-DEBUG: 05:02:06.617: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.617: Processing command SLEEP 1500 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.617: Sleeping 1500ms 307s (process:2466): libfprint-device-DEBUG: 05:02:06.917: Idle cancelling on ongoing operation! 307s (process:2466): libfprint-virtual_device-DEBUG: 05:02:06.917: Got cancellation! 307s (process:2466): libfprint-device-DEBUG: 05:02:06.917: Device reported finger status change: FP_FINGER_STATUS_NEEDED 307s (process:2466): libfprint-device-DEBUG: 05:02:06.917: Device reported identify completion 307s (process:2466): libfprint-device-DEBUG: 05:02:06.917: Device reported finger status change: FP_FINGER_STATUS_NONE 307s (process:2466): libfprint-device-DEBUG: 05:02:06.917: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 307s (process:2466): libfprint-device-DEBUG: 05:02:06.917: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:07.117: Got a new connection! 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.118: Got instructions of length 5 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.118: Received command CONT 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.118: Processing command CONT 308s (process:2466): libfprint-device-DEBUG: 05:02:07.118: Device reported deletion completion 308s (process:2466): libfprint-device-DEBUG: 05:02:07.118: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 308s (process:2466): libfprint-device-DEBUG: 05:02:07.118: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:07.118: Got a new connection! 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.118: Got instructions of length 16 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.118: Received command SET_KEEP_ALIVE 0 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.118: Keep alive toggled: 0 308s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:07.119: Got a new connection! 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.119: Got instructions of length 19 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.119: Received command SET_ENROLL_STAGES 5 308s (process:2466): libfprint-device-DEBUG: 05:02:07.119: Device reported close completion 308s (process:2466): libfprint-device-DEBUG: 05:02:07.119: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 308s (process:2466): libfprint-device-DEBUG: 05:02:07.119: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s ok 308s test_device_sleep_before_completing_verify (__main__.VirtualDeviceStorage.test_device_sleep_before_completing_verify) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.120: 85038206: ../libfprint/drivers/virtual-device.c:387 308s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:07.120: 85038242: ../libfprint/drivers/virtual-device-listener.c:153 308s (process:2466): libfprint-device-DEBUG: 05:02:07.120: Device reported open completion 308s (process:2466): libfprint-device-DEBUG: 05:02:07.120: Completing action FPI_DEVICE_ACTION_OPEN in idle! 308s (process:2466): libfprint-device-DEBUG: 05:02:07.120: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:07.120: Got a new connection! 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.120: Got instructions of length 14 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.120: Received command SCAN foo-print 308s (process:2466): libfprint-device-DEBUG: 05:02:07.121: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.121: Processing command SCAN foo-print 308s (process:2466): libfprint-device-DEBUG: 05:02:07.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2466): libfprint-device-DEBUG: 05:02:07.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2466): libfprint-device-DEBUG: 05:02:07.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2466): libfprint-device-DEBUG: 05:02:07.121: Device reported enroll progress, reported 1 of 5 have been completed 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.121: Sleeping completed 308s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:07.121: Got a new connection! 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.121: Got instructions of length 14 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.121: Received command SCAN foo-print 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.121: Processing command SCAN foo-print 308s (process:2466): libfprint-device-DEBUG: 05:02:07.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2466): libfprint-device-DEBUG: 05:02:07.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2466): libfprint-device-DEBUG: 05:02:07.121: Device reported enroll progress, reported 2 of 5 have been completed 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.121: Sleeping completed 308s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:07.121: Got a new connection! 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.121: Got instructions of length 14 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.121: Received command SCAN foo-print 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.121: Processing command SCAN foo-print 308s (process:2466): libfprint-device-DEBUG: 05:02:07.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2466): libfprint-device-DEBUG: 05:02:07.121: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2466): libfprint-device-DEBUG: 05:02:07.121: Device reported enroll progress, reported 3 of 5 have been completed 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.121: Sleeping completed 308s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:07.122: Got a new connection! 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.122: Got instructions of length 14 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.122: Received command SCAN foo-print 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.122: Processing command SCAN foo-print 308s (process:2466): libfprint-device-DEBUG: 05:02:07.122: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2466): libfprint-device-DEBUG: 05:02:07.122: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2466): libfprint-device-DEBUG: 05:02:07.122: Device reported enroll progress, reported 4 of 5 have been completed 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.122: Sleeping completed 308s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:07.122: Got a new connection! 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.122: Got instructions of length 14 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.122: Received command SCAN foo-print 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.122: Processing command SCAN foo-print 308s (process:2466): libfprint-device-DEBUG: 05:02:07.122: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2466): libfprint-device-DEBUG: 05:02:07.122: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2466): libfprint-device-DEBUG: 05:02:07.122: Device reported enroll progress, reported 5 of 5 have been completed 308s (process:2466): libfprint-device-DEBUG: 05:02:07.122: Device reported enroll completion 308s (process:2466): libfprint-device-DEBUG: 05:02:07.122: Device reported finger status change: FP_FINGER_STATUS_NONE 308s (process:2466): libfprint-device-DEBUG: 05:02:07.122: Print for finger FP_FINGER_LEFT_RING enrolled 308s (process:2466): libfprint-device-DEBUG: 05:02:07.122: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 308s (process:2466): libfprint-device-DEBUG: 05:02:07.122: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:07.122: Got a new connection! 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.123: Got instructions of length 9 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.123: Received command SLEEP 100 308s (process:2466): libfprint-device-DEBUG: 05:02:07.123: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.123: Processing command SLEEP 100 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.123: Sleeping 100ms 308s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:07.123: Got a new connection! 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.123: Got instructions of length 14 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.123: Received command SCAN bar-print 308s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:07.123: Got a new connection! 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.123: Got instructions of length 9 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.123: Received command SLEEP 800 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.223: Sleeping completed 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.223: Processing command SCAN bar-print 308s (process:2466): libfprint-device-DEBUG: 05:02:07.223: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2466): libfprint-device-DEBUG: 05:02:07.223: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 308s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:07.223: Trying to identify print 'bar-print' against a gallery of 1 prints 308s (process:2466): libfprint-device-DEBUG: 05:02:07.223: Device reported identify result 308s (process:2466): libfprint-device-DEBUG: 05:02:07.223: Device reported finger status change: FP_FINGER_STATUS_NEEDED 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.223: Processing command SLEEP 800 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.223: Sleeping 800ms 308s (process:2466): libfprint-virtual_device-DEBUG: 05:02:07.223: Sleeping now, command queued for later: SCAN bar-print 308s (process:2466): libfprint-device-DEBUG: 05:02:07.461: Updated temperature model after 0.34 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.024: Sleeping completed 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.024: Processing command SCAN bar-print 309s (process:2466): libfprint-device-DEBUG: 05:02:08.024: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 309s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:08.024: Trying to identify print 'bar-print' against a gallery of 1 prints 309s (process:2466): libfprint-device-DEBUG: 05:02:08.024: Device reported finger status change: FP_FINGER_STATUS_NEEDED 309s (process:2466): libfprint-device-DEBUG: 05:02:08.024: Device reported identify completion 309s (process:2466): libfprint-device-DEBUG: 05:02:08.024: Device reported finger status change: FP_FINGER_STATUS_NONE 309s (process:2466): libfprint-device-DEBUG: 05:02:08.024: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 309s (process:2466): libfprint-device-DEBUG: 05:02:08.024: Updated temperature model after 0.56 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 309s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:08.024: Got a new connection! 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.024: Got instructions of length 5 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.024: Received command CONT 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.024: Processing command CONT 309s (process:2466): libfprint-device-DEBUG: 05:02:08.025: Device reported deletion completion 309s (process:2466): libfprint-device-DEBUG: 05:02:08.025: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 309s (process:2466): libfprint-device-DEBUG: 05:02:08.025: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 309s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:08.025: Got a new connection! 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.025: Got instructions of length 16 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.025: Received command SET_KEEP_ALIVE 0 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.025: Keep alive toggled: 0 309s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:08.025: Got a new connection! 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.025: Got instructions of length 19 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.025: Received command SET_ENROLL_STAGES 5 309s (process:2466): libfprint-device-DEBUG: 05:02:08.025: Device reported close completion 309s (process:2466): libfprint-device-DEBUG: 05:02:08.025: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 309s (process:2466): libfprint-device-DEBUG: 05:02:08.025: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 309s Enroll done 309s ok 309s test_device_sleep_on_cancellation (__main__.VirtualDeviceStorage.test_device_sleep_on_cancellation) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.026: 85944190: ../libfprint/drivers/virtual-device.c:387 309s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:08.026: 85944208: ../libfprint/drivers/virtual-device-listener.c:153 309s (process:2466): libfprint-device-DEBUG: 05:02:08.026: Device reported open completion 309s (process:2466): libfprint-device-DEBUG: 05:02:08.026: Completing action FPI_DEVICE_ACTION_OPEN in idle! 309s (process:2466): libfprint-device-DEBUG: 05:02:08.026: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 309s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:08.026: Got a new connection! 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.026: Got instructions of length 26 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.026: Received command SET_CANCELLATION_ENABLED 0 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.026: Cancellation support toggled: 0 309s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:08.026: Got a new connection! 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.026: Got instructions of length 10 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.026: Received command SLEEP 1500 309s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:08.027: Got a new connection! 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.027: Got instructions of length 14 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.027: Received command SCAN foo-print 309s (process:2466): libfprint-device-DEBUG: 05:02:08.027: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.027: Processing command SLEEP 1500 309s (process:2466): libfprint-virtual_device-DEBUG: 05:02:08.027: Sleeping 1500ms 309s (process:2466): libfprint-device-DEBUG: 05:02:08.327: Idle cancelling on ongoing operation! 310s Executing: libfprint-2/virtual-device.test 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.528: Sleeping completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.528: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.528: Device reported identify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.528: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.528: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.529: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.529: Processing command SCAN foo-print 310s (process:2466): libfprint-device-DEBUG: 05:02:09.529: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.529: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.529: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s ok 310s test_duplicate_enroll (__main__.VirtualDeviceStorage.test_duplicate_enroll) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.530: 87448997: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.531: 87449171: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.531: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.531: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.531: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.532: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.532: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.532: Received command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.532: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.532: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.532: Device reported enroll progress, reported 1 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.532: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.533: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.533: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.533: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.533: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.533: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.533: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.533: Device reported enroll progress, reported 2 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.534: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.534: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.535: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.535: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.535: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.535: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.535: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.535: Device reported enroll progress, reported 3 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.535: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.536: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.536: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.536: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.536: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.536: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.536: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.536: Device reported enroll progress, reported 4 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.537: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.537: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.537: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.538: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.538: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.538: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.538: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.538: Device reported enroll progress, reported 5 of 5 have been completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.538: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.538: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.538: Print for finger FP_FINGER_LEFT_LITTLE enrolled 310s (process:2466): libfprint-device-DEBUG: 05:02:09.538: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.538: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.539: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.539: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.539: Received command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.540: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.540: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.540: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.540: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.540: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.540: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.540: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.540: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.541: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.541: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.542: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.542: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.542: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.542: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.542: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.542: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.543: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.543: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.543: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.543: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.543: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.544: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.544: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.544: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.544: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s Enroll done 310s Enroll done 310s ok 310s test_enroll (__main__.VirtualDeviceStorage.test_enroll) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.544: 87462860: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.544: 87462884: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.545: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.545: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.545: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.546: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.546: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.546: Received command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.546: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.546: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.546: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.546: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.546: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.546: Device reported enroll progress, reported 1 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.546: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.547: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.547: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.547: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.547: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.547: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.547: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.547: Device reported enroll progress, reported 2 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.547: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.548: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.548: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.548: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.548: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.548: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.548: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.548: Device reported enroll progress, reported 3 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.548: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.549: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.549: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.549: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.549: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.549: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.549: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.549: Device reported enroll progress, reported 4 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.549: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.550: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.550: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.550: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.550: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.550: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.550: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.550: Device reported enroll progress, reported 5 of 5 have been completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.550: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.550: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.550: Print for finger FP_FINGER_LEFT_LITTLE enrolled 310s (process:2466): libfprint-device-DEBUG: 05:02:09.550: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.550: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.551: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.552: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.552: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.552: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.552: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.552: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.552: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.552: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.552: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.553: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.553: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.553: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.553: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.553: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.553: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.553: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.553: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s Enroll done 310s ok 310s test_enroll_script (__main__.VirtualDeviceStorage.test_enroll_script) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.554: 87472534: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.554: 87472591: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.554: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.554: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.555: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.555: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.555: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.555: Received command SET_ENROLL_STAGES 8 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.556: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.556: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.556: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.556: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.556: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.556: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.557: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.557: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.557: Received command RETRY 1 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.557: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.558: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.558: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.558: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.558: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.558: Received command RETRY 3 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.558: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.558: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.558: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.559: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.559: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.559: Received command RETRY 2 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.559: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.559: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.559: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.560: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.560: Got instructions of length 8 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.560: Received command SLEEP 10 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.560: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.560: Got instructions of length 8 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.560: Received command SLEEP 20 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.561: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.561: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.561: Received command RETRY 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.561: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.561: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.561: Received command RETRY 3 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.562: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.562: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.562: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.562: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.562: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.562: Received command SCAN another-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.562: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.562: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.562: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.563: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Received command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported enroll progress, reported 1 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported enroll progress, reported 2 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Processing command RETRY 1 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported enroll progress, reported 2 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported enroll progress, reported 3 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Processing command RETRY 3 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported enroll progress, reported 3 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported enroll progress, reported 4 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Processing command RETRY 2 310s (process:2466): libfprint-device-DEBUG: 05:02:09.563: Device reported enroll progress, reported 4 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.563: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.564: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.564: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.564: Device reported enroll progress, reported 5 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.564: Processing command SLEEP 10 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.564: Sleeping 10ms 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.574: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.574: Processing command SLEEP 20 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.574: Sleeping 20ms 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.594: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.594: Processing command RETRY 0 310s (process:2466): libfprint-device-DEBUG: 05:02:09.594: Device reported enroll progress, reported 5 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.594: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.594: Processing command RETRY 3 310s (process:2466): libfprint-device-DEBUG: 05:02:09.594: Device reported enroll progress, reported 5 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.594: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.594: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.594: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.595: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.595: Device reported enroll progress, reported 6 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.595: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.595: Processing command SCAN another-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.595: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.595: Device reported enroll progress, reported 6 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.595: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.595: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.595: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.595: Device reported enroll progress, reported 7 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.595: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.595: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.595: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.595: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.595: Device reported enroll progress, reported 8 of 8 have been completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.595: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.595: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.595: Print for finger FP_FINGER_UNKNOWN enrolled 310s (process:2466): libfprint-device-DEBUG: 05:02:09.595: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.595: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.596: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.596: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.596: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.596: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.596: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.596: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.596: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.597: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.597: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.598: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.598: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.598: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.598: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.598: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.598: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.598: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.598: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s ok 310s test_enroll_script_interactive (__main__.VirtualDeviceStorage.test_enroll_script_interactive) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.599: 87517458: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.599: 87517505: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.599: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.599: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.599: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.600: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.600: Got instructions of length 8 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.600: Received command SLEEP 50 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.600: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.601: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.601: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.601: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.601: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.601: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.601: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.601: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.601: Received command RETRY 1 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.602: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.602: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.602: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.602: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.602: Got instructions of length 8 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.602: Received command SLEEP 50 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.602: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.603: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.603: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.603: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.603: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.603: Received command RETRY 2 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.603: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.603: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.603: Received command SCAN another-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.604: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.604: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.604: Received command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.604: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.604: Processing command SLEEP 50 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.604: Sleeping 50ms 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.654: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.655: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.655: Device reported enroll progress, reported 1 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.655: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.655: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.655: Device reported enroll progress, reported 2 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.655: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.655: Processing command RETRY 1 310s (process:2466): libfprint-device-DEBUG: 05:02:09.655: Device reported enroll progress, reported 2 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.655: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.655: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.655: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.655: Device reported enroll progress, reported 3 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.655: Processing command SLEEP 50 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.655: Sleeping 50ms 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.706: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.706: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.706: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.706: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.706: Device reported enroll progress, reported 4 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.706: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.706: Processing command RETRY 2 310s (process:2466): libfprint-device-DEBUG: 05:02:09.706: Device reported enroll progress, reported 4 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.706: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.706: Processing command SCAN another-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.706: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.706: Device reported enroll progress, reported 4 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.706: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.706: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.706: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.707: Device reported enroll progress, reported 5 of 5 have been completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.707: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.707: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.707: Print for finger FP_FINGER_UNKNOWN enrolled 310s (process:2466): libfprint-device-DEBUG: 05:02:09.707: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.707: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.708: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.708: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.708: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.708: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.708: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.709: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.709: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.709: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.709: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.710: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.710: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.710: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.710: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.710: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.711: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.711: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.711: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s ok 310s test_enroll_verify_error (__main__.VirtualDeviceStorage.test_enroll_verify_error) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.711: 87629817: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.711: 87629886: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.712: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.712: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.712: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.713: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.713: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.713: Received command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.713: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.713: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.713: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.713: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.713: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.713: Device reported enroll progress, reported 1 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.714: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.714: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.714: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.714: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.714: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.715: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.715: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.715: Device reported enroll progress, reported 2 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.715: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.716: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.716: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.716: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.716: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.716: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.716: Device reported enroll progress, reported 3 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.716: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.717: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.717: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.717: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.717: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.717: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.717: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.717: Device reported enroll progress, reported 4 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.717: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.718: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.718: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.718: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.718: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.718: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.718: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.718: Device reported enroll progress, reported 5 of 5 have been completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.718: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.718: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.718: Print for finger FP_FINGER_LEFT_RING enrolled 310s (process:2466): libfprint-device-DEBUG: 05:02:09.718: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.718: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.719: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.720: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.720: Received command ERROR 0 310s (process:2466): libfprint-device-DEBUG: 05:02:09.720: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.720: Processing command ERROR 0 310s (process:2466): libfprint-device-DEBUG: 05:02:09.720: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.720: Device reported identify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.720: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.720: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.720: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.721: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.721: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.721: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.721: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.721: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.721: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.721: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.722: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.722: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.722: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.722: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.722: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.722: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.722: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.723: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.723: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.723: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s Enroll done 310s ok 310s test_enroll_verify_match (__main__.VirtualDeviceStorage.test_enroll_verify_match) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.723: 87641893: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.723: 87641922: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.724: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.724: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.724: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.724: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.725: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.725: Received command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.725: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.725: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.725: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.725: Device reported enroll progress, reported 1 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.725: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.726: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.726: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.726: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.726: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.726: Device reported enroll progress, reported 2 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.726: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.727: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.727: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.727: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.727: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.727: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.727: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.727: Device reported enroll progress, reported 3 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.727: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.728: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.728: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.728: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.728: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.728: Device reported enroll progress, reported 4 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.728: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.729: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.729: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.729: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.729: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.729: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.730: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.730: Device reported enroll progress, reported 5 of 5 have been completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.730: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.730: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.730: Print for finger FP_FINGER_LEFT_THUMB enrolled 310s (process:2466): libfprint-device-DEBUG: 05:02:09.730: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.730: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.731: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.732: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.732: Received command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.732: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.732: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.732: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.732: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:09.732: Trying to identify print 'testprint' against a gallery of 1 prints 310s (process:2466): libfprint-device-DEBUG: 05:02:09.732: Device reported identify result 310s (process:2466): libfprint-device-DEBUG: 05:02:09.732: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.732: Device reported identify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.732: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.732: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.732: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.733: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.733: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.733: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.733: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.733: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.733: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.733: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.734: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.734: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.734: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.734: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.735: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.735: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.735: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.735: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.735: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.735: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s Enroll done 310s ok 310s test_enroll_verify_no_match (__main__.VirtualDeviceStorage.test_enroll_verify_no_match) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.736: 87654526: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.736: 87654580: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.736: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.736: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.736: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.737: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.737: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.737: Received command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.738: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.738: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.738: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.738: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.738: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.738: Device reported enroll progress, reported 1 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.738: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.738: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.739: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.739: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.739: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.739: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.739: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.739: Device reported enroll progress, reported 2 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.739: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.739: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.739: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.740: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.740: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.740: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.740: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.740: Device reported enroll progress, reported 3 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.740: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.740: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.740: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.741: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.741: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.741: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.741: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.741: Device reported enroll progress, reported 4 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.741: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.741: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.741: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.741: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.742: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.742: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.742: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.742: Device reported enroll progress, reported 5 of 5 have been completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.742: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.742: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.742: Print for finger FP_FINGER_LEFT_RING enrolled 310s (process:2466): libfprint-device-DEBUG: 05:02:09.742: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.742: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.743: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.743: Got instructions of length 18 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.743: Received command SCAN not-testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.743: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.743: Processing command SCAN not-testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.743: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.743: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:09.743: Trying to identify print 'not-testprint' against a gallery of 1 prints 310s (process:2466): libfprint-device-DEBUG: 05:02:09.743: Device reported identify result 310s (process:2466): libfprint-device-DEBUG: 05:02:09.743: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.743: Device reported identify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.743: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.743: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.743: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.744: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.744: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.744: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.744: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.745: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.745: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.745: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.745: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.745: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.745: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.745: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.746: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.746: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.746: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.746: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.746: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.746: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s Enroll done 310s ok 310s test_enroll_verify_retry (__main__.VirtualDeviceStorage.test_enroll_verify_retry) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.746: 87664982: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.746: 87665165: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.747: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.747: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.747: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.748: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.748: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.748: Received command RETRY 1 310s (process:2466): libfprint-device-DEBUG: 05:02:09.748: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.748: Processing command RETRY 1 310s (process:2466): libfprint-device-DEBUG: 05:02:09.748: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.748: Virtual device scan failed with error: The swipe was too short, please try again. 310s (process:2466): libfprint-device-DEBUG: 05:02:09.748: Device reported verify result 310s (process:2466): libfprint-device-DEBUG: 05:02:09.748: Device reported verify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.748: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.748: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.748: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.749: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.749: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.749: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.749: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.749: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.749: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.749: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.750: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.750: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.750: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.750: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.750: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.750: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.750: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.751: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.751: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.751: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s ok 310s test_enroll_verify_script (__main__.VirtualDeviceStorage.test_enroll_verify_script) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.751: 87669713: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.751: 87669757: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.752: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.752: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.752: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.752: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.752: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.752: Received command SET_ENROLL_STAGES 8 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.753: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.753: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.753: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.753: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.753: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.753: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.754: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.754: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.754: Received command RETRY 1 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.754: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.754: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.754: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.754: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.755: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.755: Received command RETRY 3 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.755: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.755: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.755: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.755: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.755: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.755: Received command RETRY 2 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.756: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.756: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.756: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.756: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.756: Got instructions of length 8 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.756: Received command SLEEP 10 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.757: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.757: Got instructions of length 8 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.757: Received command SLEEP 20 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.757: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.757: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.757: Received command RETRY 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.757: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.758: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.758: Received command RETRY 3 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.758: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.758: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.758: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.758: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.758: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.758: Received command SCAN another-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.759: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.759: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.759: Received command SCAN print-id 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.759: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.759: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.759: Received command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.759: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.759: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.759: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.759: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.759: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.759: Device reported enroll progress, reported 1 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported enroll progress, reported 2 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Processing command RETRY 1 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported enroll progress, reported 2 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported enroll progress, reported 3 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Processing command RETRY 3 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported enroll progress, reported 3 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported enroll progress, reported 4 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Processing command RETRY 2 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported enroll progress, reported 4 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.760: Device reported enroll progress, reported 5 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Processing command SLEEP 10 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.760: Sleeping 10ms 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.770: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.770: Processing command SLEEP 20 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.770: Sleeping 20ms 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.791: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.791: Processing command RETRY 0 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Device reported enroll progress, reported 5 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.791: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.791: Processing command RETRY 3 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Device reported enroll progress, reported 5 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.791: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.791: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Device reported enroll progress, reported 6 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.791: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.791: Processing command SCAN another-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Device reported enroll progress, reported 6 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.791: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.791: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Device reported enroll progress, reported 7 of 8 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.791: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.791: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Device reported enroll progress, reported 8 of 8 have been completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Print for finger FP_FINGER_UNKNOWN enrolled 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.791: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.792: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.792: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.792: Received command RETRY 2 310s (process:2466): libfprint-device-DEBUG: 05:02:09.793: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.793: Processing command RETRY 2 310s (process:2466): libfprint-device-DEBUG: 05:02:09.793: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.793: Virtual device scan failed with error: The finger was not centered properly, please try again. 310s (process:2466): libfprint-device-DEBUG: 05:02:09.793: Device reported verify result 310s (process:2466): libfprint-device-DEBUG: 05:02:09.793: Device reported verify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.793: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.793: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.793: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.794: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.794: Got instructions of length 8 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.794: Received command SLEEP 50 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.794: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.795: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.795: Received command RETRY 1 310s (process:2466): libfprint-device-DEBUG: 05:02:09.795: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.795: Processing command SLEEP 50 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.795: Sleeping 50ms 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.845: Sleeping completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.845: Processing command RETRY 1 310s (process:2466): libfprint-device-DEBUG: 05:02:09.845: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.845: Virtual device scan failed with error: The swipe was too short, please try again. 310s (process:2466): libfprint-device-DEBUG: 05:02:09.845: Device reported verify result 310s (process:2466): libfprint-device-DEBUG: 05:02:09.845: Device reported verify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.846: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.846: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.846: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.847: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.847: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.847: Received command SCAN another-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.847: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.847: Processing command SCAN another-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.847: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.847: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.847: Virtual device scanned print another-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.847: Device reported verify result 310s (process:2466): libfprint-device-DEBUG: 05:02:09.847: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.847: Device reported verify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.847: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.847: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.847: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.848: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.849: Got instructions of length 13 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.849: Received command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.849: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.849: Processing command SCAN print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.849: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.849: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.849: Virtual device scanned print print-id 310s (process:2466): libfprint-device-DEBUG: 05:02:09.849: Device reported verify result 310s (process:2466): libfprint-device-DEBUG: 05:02:09.849: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.849: Device reported verify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.849: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.849: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.849: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.850: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.850: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.850: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.850: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.851: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.851: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.851: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.851: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.851: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.851: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.851: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.852: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.852: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.852: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.852: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.852: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.852: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s ok 310s test_enroll_with_retry (__main__.VirtualDeviceStorage.test_enroll_with_retry) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.853: 87771554: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.853: 87771603: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.853: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.853: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.854: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.854: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.855: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.855: Received command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.855: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.855: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.855: Device reported enroll progress, reported 1 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.855: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.856: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.856: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.856: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.856: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.856: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.856: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.856: Device reported enroll progress, reported 2 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.856: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.857: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.857: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.857: Received command RETRY 1 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.857: Processing command RETRY 1 310s (process:2466): libfprint-device-DEBUG: 05:02:09.857: Device reported enroll progress, reported 2 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.858: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.858: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.859: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.859: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.859: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.859: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.859: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.859: Device reported enroll progress, reported 3 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.859: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.859: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.860: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.860: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.860: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.860: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.860: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.860: Device reported enroll progress, reported 4 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.860: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.861: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.861: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.861: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.861: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.861: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.861: Device reported enroll progress, reported 5 of 5 have been completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.861: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.861: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.861: Print for finger FP_FINGER_LEFT_LITTLE enrolled 310s (process:2466): libfprint-device-DEBUG: 05:02:09.861: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.861: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.862: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.863: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.863: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.863: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.863: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.863: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.863: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.863: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.864: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.864: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.864: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.864: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.864: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.864: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.865: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.865: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.865: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s Enroll done 310s ok 310s test_finger_status (__main__.VirtualDeviceStorage.test_finger_status) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.865: 87783779: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.865: 87783843: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.866: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.866: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.866: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-device-DEBUG: 05:02:09.866: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-device-DEBUG: 05:02:09.866: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.867: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.867: Got instructions of length 8 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.867: Received command FINGER 1 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.867: Processing command FINGER 1 310s (process:2466): libfprint-device-DEBUG: 05:02:09.867: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.868: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.868: Got instructions of length 8 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.868: Received command FINGER 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.868: Processing command FINGER 0 310s (process:2466): libfprint-device-DEBUG: 05:02:09.868: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.868: Idle cancelling on ongoing operation! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.868: Got cancellation! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.868: Device reported identify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.868: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.869: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.869: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.869: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.869: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.870: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.870: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.870: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.870: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.870: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.870: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.870: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.871: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.871: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.871: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.871: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.871: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.871: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.872: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.872: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s ok 310s test_finger_status_after_sleep (__main__.VirtualDeviceStorage.test_finger_status_after_sleep) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.872: 87790596: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.872: 87790654: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.872: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.873: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.873: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.873: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.874: Got instructions of length 8 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.874: Received command SLEEP 10 310s (process:2466): libfprint-device-DEBUG: 05:02:09.874: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.874: Processing command SLEEP 10 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.874: Sleeping 10ms 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.884: Sleeping completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.885: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.885: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.886: Got instructions of length 8 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.886: Received command FINGER 1 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.886: Processing command FINGER 1 310s (process:2466): libfprint-device-DEBUG: 05:02:09.886: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.886: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.887: Got instructions of length 8 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.887: Received command FINGER 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.887: Processing command FINGER 0 310s (process:2466): libfprint-device-DEBUG: 05:02:09.887: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.887: Idle cancelling on ongoing operation! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.887: Got cancellation! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.887: Device reported identify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.887: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.887: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.887: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.888: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.888: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.888: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.888: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.888: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.889: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.889: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.889: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.889: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.889: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.889: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.890: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.890: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.890: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.890: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.890: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.890: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s ok 310s test_identify_match (__main__.VirtualDeviceStorage.test_identify_match) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.891: 87809527: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.891: 87809579: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.891: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.892: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.892: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.892: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.893: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.893: Received command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.893: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.893: Processing command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.893: Device reported enroll progress, reported 1 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.893: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.894: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.894: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.894: Received command SCAN right-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.894: Processing command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.894: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.894: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.894: Device reported enroll progress, reported 2 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.894: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.895: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.895: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.895: Received command SCAN right-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.895: Processing command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.895: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.895: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.895: Device reported enroll progress, reported 3 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.895: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.896: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.896: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.896: Received command SCAN right-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.896: Processing command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.896: Device reported enroll progress, reported 4 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.896: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.897: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.897: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.897: Received command SCAN right-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.897: Processing command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.897: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.897: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.897: Device reported enroll progress, reported 5 of 5 have been completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.897: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.897: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.897: Print for finger FP_FINGER_RIGHT_THUMB enrolled 310s (process:2466): libfprint-device-DEBUG: 05:02:09.897: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.897: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.898: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.898: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.898: Received command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.899: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.899: Processing command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.899: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.899: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.899: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.899: Device reported enroll progress, reported 1 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.899: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.899: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.900: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.900: Received command SCAN left-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.900: Processing command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.900: Device reported enroll progress, reported 2 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.900: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.900: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.901: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.901: Received command SCAN left-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.901: Processing command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.901: Device reported enroll progress, reported 3 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.901: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.902: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.902: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.902: Received command SCAN left-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.902: Processing command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.902: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.902: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.902: Device reported enroll progress, reported 4 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.902: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.902: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.902: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.902: Received command SCAN left-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.902: Processing command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.902: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.902: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.902: Device reported enroll progress, reported 5 of 5 have been completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.902: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.902: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.902: Print for finger FP_FINGER_LEFT_THUMB enrolled 310s (process:2466): libfprint-device-DEBUG: 05:02:09.902: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.902: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.903: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.903: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.903: Received command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.903: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.903: Processing command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.903: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.903: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:09.903: Trying to identify print 'right-thumb' against a gallery of 2 prints 310s (process:2466): libfprint-device-DEBUG: 05:02:09.903: Device reported identify result 310s (process:2466): libfprint-device-DEBUG: 05:02:09.903: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.903: Device reported identify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.903: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.903: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.903: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.903: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.903: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.903: Received command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.904: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.904: Processing command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.904: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.904: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:09.904: Trying to identify print 'left-thumb' against a gallery of 2 prints 310s (process:2466): libfprint-device-DEBUG: 05:02:09.904: Device reported identify result 310s (process:2466): libfprint-device-DEBUG: 05:02:09.904: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.904: Device reported identify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.904: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.904: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.904: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.904: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.904: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.904: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.904: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.904: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.904: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.904: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.904: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.904: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.904: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.904: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.904: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.905: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.905: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.905: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.905: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.905: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s Enroll done 310s Enroll done 310s ok 310s test_identify_missing_print (__main__.VirtualDeviceStorage.test_identify_missing_print) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.905: 87823616: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.905: 87823636: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.905: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.905: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.905: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.905: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.906: Got instructions of length 23 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.906: Received command SCAN not-existing-print 310s (process:2466): libfprint-device-DEBUG: 05:02:09.906: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.906: Processing command SCAN not-existing-print 310s (process:2466): libfprint-device-DEBUG: 05:02:09.906: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.906: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:09.906: Trying to identify print 'not-existing-print' against a gallery of 1 prints 310s (process:2466): libfprint-device-DEBUG: 05:02:09.906: Device reported identify result 310s (process:2466): libfprint-device-DEBUG: 05:02:09.906: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.906: Device reported identify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.906: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.906: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.906: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.906: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.906: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.906: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.906: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.906: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.906: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.906: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.906: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.906: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.906: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.906: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.907: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.907: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.907: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.907: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.907: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.907: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s ok 310s test_identify_no_match (__main__.VirtualDeviceStorage.test_identify_no_match) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.907: 87825902: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.907: 87825922: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.907: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.908: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.908: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.908: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.908: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.908: Received command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.908: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.908: Processing command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.908: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.908: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.908: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.908: Device reported enroll progress, reported 1 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.908: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.908: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.908: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.908: Received command SCAN right-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.908: Processing command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.908: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.908: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.908: Device reported enroll progress, reported 2 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.908: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.909: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.909: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.909: Received command SCAN right-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.909: Processing command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.909: Device reported enroll progress, reported 3 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.909: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.909: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.909: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.909: Received command SCAN right-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.909: Processing command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.909: Device reported enroll progress, reported 4 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.909: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.909: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.909: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.909: Received command SCAN right-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.909: Processing command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.909: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.909: Device reported enroll progress, reported 5 of 5 have been completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.909: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.910: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.910: Print for finger FP_FINGER_RIGHT_THUMB enrolled 310s (process:2466): libfprint-device-DEBUG: 05:02:09.910: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.910: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.910: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.910: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.910: Received command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.910: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.910: Processing command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.911: Device reported enroll progress, reported 1 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.911: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.911: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.911: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.911: Received command SCAN left-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.911: Processing command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.911: Device reported enroll progress, reported 2 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.911: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.911: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.911: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.911: Received command SCAN left-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.911: Processing command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.911: Device reported enroll progress, reported 3 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.911: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.912: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.912: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.912: Received command SCAN left-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.912: Processing command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.912: Device reported enroll progress, reported 4 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.912: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.912: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.912: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.912: Received command SCAN left-thumb 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.912: Processing command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.912: Device reported enroll progress, reported 5 of 5 have been completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.912: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.912: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.912: Print for finger FP_FINGER_LEFT_THUMB enrolled 310s (process:2466): libfprint-device-DEBUG: 05:02:09.912: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.912: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.912: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.912: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.913: Received command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.913: Processing command SCAN right-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:09.913: Trying to identify print 'right-thumb' against a gallery of 1 prints 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Device reported identify result 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Device reported identify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.913: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.913: Got instructions of length 15 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.913: Received command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.913: Processing command SCAN left-thumb 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:09.913: Trying to identify print 'left-thumb' against a gallery of 1 prints 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Device reported identify result 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Device reported identify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.913: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.913: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.914: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.914: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.914: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.914: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.914: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.914: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.914: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.914: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.914: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.914: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.914: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.914: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.914: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.914: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.914: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.914: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s Enroll done 310s Enroll done 310s ok 310s test_identify_retry (__main__.VirtualDeviceStorage.test_identify_retry) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.914: 87832892: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.914: 87832912: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.914: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.914: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.914: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.915: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.915: Got instructions of length 7 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.915: Received command RETRY 1 310s (process:2466): libfprint-device-DEBUG: 05:02:09.915: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.915: Processing command RETRY 1 310s (process:2466): libfprint-device-DEBUG: 05:02:09.915: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.915: Device reported identify result 310s (process:2466): libfprint-device-DEBUG: 05:02:09.915: Device reported identify completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.915: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.915: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.915: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.915: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.915: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.915: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.915: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.915: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.915: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.915: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.916: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.916: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.916: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.916: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.916: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.916: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.916: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.916: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.916: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.916: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s ok 310s test_identify_unsupported (__main__.VirtualDeviceStorage.test_identify_unsupported) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.916: 87834690: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.916: 87834701: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.916: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.916: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.916: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s skipped 'Device supports identification' 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.917: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.917: Got instructions of length 5 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.917: Received command CONT 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.917: Processing command CONT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.917: Device reported deletion completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.917: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.917: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.917: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.917: Got instructions of length 16 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.917: Received command SET_KEEP_ALIVE 0 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.917: Keep alive toggled: 0 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.917: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.917: Got instructions of length 19 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.917: Received command SET_ENROLL_STAGES 5 310s (process:2466): libfprint-device-DEBUG: 05:02:09.917: Device reported close completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.917: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.917: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s test_list_delete (__main__.VirtualDeviceStorage.test_list_delete) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.917: 87835934: ../libfprint/drivers/virtual-device.c:387 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.917: 87835943: ../libfprint/drivers/virtual-device-listener.c:153 310s (process:2466): libfprint-device-DEBUG: 05:02:09.917: Device reported open completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.918: Completing action FPI_DEVICE_ACTION_OPEN in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.918: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.918: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.918: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.918: Received command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.918: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.918: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.918: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.918: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.918: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.918: Device reported enroll progress, reported 1 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.918: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.918: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.918: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.918: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.918: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.918: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.918: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.918: Device reported enroll progress, reported 2 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.918: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.918: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.919: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.919: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.919: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.919: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.919: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.919: Device reported enroll progress, reported 3 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.919: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.919: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.919: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.919: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.919: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.919: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.919: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.919: Device reported enroll progress, reported 4 of 5 have been completed 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.919: Sleeping completed 310s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:09.919: Got a new connection! 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.919: Got instructions of length 14 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.919: Received command SCAN testprint 310s (process:2466): libfprint-virtual_device-DEBUG: 05:02:09.919: Processing command SCAN testprint 310s (process:2466): libfprint-device-DEBUG: 05:02:09.919: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 310s (process:2466): libfprint-device-DEBUG: 05:02:09.919: Device reported finger status change: FP_FINGER_STATUS_NEEDED 310s (process:2466): libfprint-device-DEBUG: 05:02:09.919: Device reported enroll progress, reported 5 of 5 have been completed 310s (process:2466): libfprint-device-DEBUG: 05:02:09.919: Device reported enroll completion 310s (process:2466): libfprint-device-DEBUG: 05:02:09.919: Device reported finger status change: FP_FINGER_STATUS_NONE 310s (process:2466): libfprint-device-DEBUG: 05:02:09.919: Print for finger FP_FINGER_RIGHT_THUMB enrolled 310s (process:2466): libfprint-device-DEBUG: 05:02:09.919: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 310s (process:2466): libfprint-device-DEBUG: 05:02:09.919: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s (process:2466): libfprint-device-DEBUG: 05:02:10.420: Device reported listing completion 311s (process:2466): libfprint-device-DEBUG: 05:02:10.420: Completing action FPI_DEVICE_ACTION_LIST in idle! 311s (process:2466): libfprint-device-DEBUG: 05:02:10.420: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 311s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:10.923: Deleting print testprint for user testuser 311s (process:2466): libfprint-device-DEBUG: 05:02:10.923: Device reported deletion completion 311s (process:2466): libfprint-device-DEBUG: 05:02:10.923: Completing action FPI_DEVICE_ACTION_DELETE in idle! 311s (process:2466): libfprint-device-DEBUG: 05:02:10.923: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 312s (process:2466): libfprint-device-DEBUG: 05:02:11.424: Device reported listing completion 312s (process:2466): libfprint-device-DEBUG: 05:02:11.424: Completing action FPI_DEVICE_ACTION_LIST in idle! 312s (process:2466): libfprint-device-DEBUG: 05:02:11.424: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 312s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:11.424: Got a new connection! 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.424: Got instructions of length 5 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.424: Received command CONT 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.424: Processing command CONT 312s (process:2466): libfprint-device-DEBUG: 05:02:11.424: Device reported deletion completion 312s (process:2466): libfprint-device-DEBUG: 05:02:11.424: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 312s (process:2466): libfprint-device-DEBUG: 05:02:11.424: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 312s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:11.424: Got a new connection! 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.425: Got instructions of length 16 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.425: Received command SET_KEEP_ALIVE 0 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.425: Keep alive toggled: 0 312s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:11.425: Got a new connection! 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.425: Got instructions of length 19 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.425: Received command SET_ENROLL_STAGES 5 312s (process:2466): libfprint-device-DEBUG: 05:02:11.425: Device reported close completion 312s (process:2466): libfprint-device-DEBUG: 05:02:11.425: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 312s (process:2466): libfprint-device-DEBUG: 05:02:11.425: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 312s Enroll done 312s 312s blub 'testprint' 312s ok 312s test_list_delete_missing (__main__.VirtualDeviceStorage.test_list_delete_missing) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.425: 89343855: ../libfprint/drivers/virtual-device.c:387 312s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:11.425: 89343873: ../libfprint/drivers/virtual-device-listener.c:153 312s (process:2466): libfprint-device-DEBUG: 05:02:11.425: Device reported open completion 312s (process:2466): libfprint-device-DEBUG: 05:02:11.425: Completing action FPI_DEVICE_ACTION_OPEN in idle! 312s (process:2466): libfprint-device-DEBUG: 05:02:11.426: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 312s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:11.426: Got a new connection! 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.426: Got instructions of length 14 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.426: Received command SCAN testprint 312s (process:2466): libfprint-device-DEBUG: 05:02:11.426: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.426: Processing command SCAN testprint 312s (process:2466): libfprint-device-DEBUG: 05:02:11.426: Device reported finger status change: FP_FINGER_STATUS_NEEDED 312s (process:2466): libfprint-device-DEBUG: 05:02:11.426: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 312s (process:2466): libfprint-device-DEBUG: 05:02:11.426: Device reported finger status change: FP_FINGER_STATUS_NEEDED 312s (process:2466): libfprint-device-DEBUG: 05:02:11.426: Device reported enroll progress, reported 1 of 5 have been completed 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.426: Sleeping completed 312s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:11.426: Got a new connection! 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.426: Got instructions of length 14 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.426: Received command SCAN testprint 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.426: Processing command SCAN testprint 312s (process:2466): libfprint-device-DEBUG: 05:02:11.426: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 312s (process:2466): libfprint-device-DEBUG: 05:02:11.426: Device reported finger status change: FP_FINGER_STATUS_NEEDED 312s (process:2466): libfprint-device-DEBUG: 05:02:11.426: Device reported enroll progress, reported 2 of 5 have been completed 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.426: Sleeping completed 312s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:11.427: Got a new connection! 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.427: Got instructions of length 14 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.427: Received command SCAN testprint 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.427: Processing command SCAN testprint 312s (process:2466): libfprint-device-DEBUG: 05:02:11.427: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 312s (process:2466): libfprint-device-DEBUG: 05:02:11.427: Device reported finger status change: FP_FINGER_STATUS_NEEDED 312s (process:2466): libfprint-device-DEBUG: 05:02:11.427: Device reported enroll progress, reported 3 of 5 have been completed 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.427: Sleeping completed 312s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:11.427: Got a new connection! 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.427: Got instructions of length 14 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.427: Received command SCAN testprint 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.427: Processing command SCAN testprint 312s (process:2466): libfprint-device-DEBUG: 05:02:11.427: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 312s (process:2466): libfprint-device-DEBUG: 05:02:11.427: Device reported finger status change: FP_FINGER_STATUS_NEEDED 312s (process:2466): libfprint-device-DEBUG: 05:02:11.427: Device reported enroll progress, reported 4 of 5 have been completed 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.427: Sleeping completed 312s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:11.427: Got a new connection! 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.428: Got instructions of length 14 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.428: Received command SCAN testprint 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.428: Processing command SCAN testprint 312s (process:2466): libfprint-device-DEBUG: 05:02:11.428: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 312s (process:2466): libfprint-device-DEBUG: 05:02:11.428: Device reported finger status change: FP_FINGER_STATUS_NEEDED 312s (process:2466): libfprint-device-DEBUG: 05:02:11.428: Device reported enroll progress, reported 5 of 5 have been completed 312s (process:2466): libfprint-device-DEBUG: 05:02:11.428: Device reported enroll completion 312s (process:2466): libfprint-device-DEBUG: 05:02:11.428: Device reported finger status change: FP_FINGER_STATUS_NONE 312s (process:2466): libfprint-device-DEBUG: 05:02:11.428: Print for finger FP_FINGER_RIGHT_THUMB enrolled 312s (process:2466): libfprint-device-DEBUG: 05:02:11.428: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 312s (process:2466): libfprint-device-DEBUG: 05:02:11.428: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 312s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:11.428: Got a new connection! 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.428: Got instructions of length 16 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.428: Received command REMOVE testprint 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.428: Processing command REMOVE testprint 312s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:11.929: Deleting print testprint for user testuser 312s (process:2466): libfprint-device-DEBUG: 05:02:11.929: Device reported deletion completion 312s (process:2466): libfprint-device-DEBUG: 05:02:11.929: Completing action FPI_DEVICE_ACTION_DELETE in idle! 312s (process:2466): libfprint-device-DEBUG: 05:02:11.929: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 312s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:11.929: Got a new connection! 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.929: Got instructions of length 5 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.929: Received command CONT 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.930: Processing command CONT 312s (process:2466): libfprint-device-DEBUG: 05:02:11.930: Device reported deletion completion 312s (process:2466): libfprint-device-DEBUG: 05:02:11.930: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 312s (process:2466): libfprint-device-DEBUG: 05:02:11.930: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 312s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:11.930: Got a new connection! 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.930: Got instructions of length 16 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.930: Received command SET_KEEP_ALIVE 0 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.930: Keep alive toggled: 0 312s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:11.930: Got a new connection! 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.930: Got instructions of length 19 312s (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.930: Received command SET_ENROLL_STAGES 5 312s (process:2466): libfprint-device-DEBUG: 05:02:11.930: Device reported close completion 312s (process:2466): libfprint-device-DEBUG: 05:02:11.930: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 312s (process:2466): libfprint-device-DEBUG: 05:02:11.930: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 312s Enroll done 312s ok 312s test_list_empty (__main__.VirtualDeviceStorage.test_list_empty) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:11.931: 89849363: ../libfprint/drivers/virtual-device.c:387 312s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:11.931: 89849381: ../libfprint/drivers/virtual-device-listener.c:153 312s (process:2466): libfprint-device-DEBUG: 05:02:11.931: Device reported open completion 312s (process:2466): libfprint-device-DEBUG: 05:02:11.931: Completing action FPI_DEVICE_ACTION_OPEN in idle! 312s (process:2466): libfprint-device-DEBUG: 05:02:11.931: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 313s (process:2466): libfprint-device-DEBUG: 05:02:12.432: Device reported listing completion 313s (process:2466): libfprint-device-DEBUG: 05:02:12.432: Completing action FPI_DEVICE_ACTION_LIST in idle! 313s (process:2466): libfprint-device-DEBUG: 05:02:12.432: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.432: Got a new connection! 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.432: Got instructions of length 5 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.432: Received command CONT 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.432: Processing command CONT 313s (process:2466): libfprint-device-DEBUG: 05:02:12.432: Device reported deletion completion 313s (process:2466): libfprint-device-DEBUG: 05:02:12.432: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 313s (process:2466): libfprint-device-DEBUG: 05:02:12.432: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.433: Got a new connection! 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.433: Got instructions of length 16 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.433: Received command SET_KEEP_ALIVE 0 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.433: Keep alive toggled: 0 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.433: Got a new connection! 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.433: Got instructions of length 19 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.433: Received command SET_ENROLL_STAGES 5 313s (process:2466): libfprint-device-DEBUG: 05:02:12.433: Device reported close completion 313s (process:2466): libfprint-device-DEBUG: 05:02:12.433: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 313s (process:2466): libfprint-device-DEBUG: 05:02:12.433: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 313s ok 313s test_list_error (__main__.VirtualDeviceStorage.test_list_error) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.433: 90351793: ../libfprint/drivers/virtual-device.c:387 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.433: 90351808: ../libfprint/drivers/virtual-device-listener.c:153 313s (process:2466): libfprint-device-DEBUG: 05:02:12.433: Device reported open completion 313s (process:2466): libfprint-device-DEBUG: 05:02:12.433: Completing action FPI_DEVICE_ACTION_OPEN in idle! 313s (process:2466): libfprint-device-DEBUG: 05:02:12.433: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.434: Got a new connection! 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.434: Got instructions of length 9 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.434: Received command SLEEP 100 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.434: Got a new connection! 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.434: Got instructions of length 7 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.434: Received command ERROR 4 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.434: Processing command SLEEP 100 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.434: Sleeping 100ms 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.534: Sleeping completed 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.534: Processing command ERROR 4 313s (process:2466): libfprint-device-DEBUG: 05:02:12.534: Device reported listing completion 313s (process:2466): libfprint-device-DEBUG: 05:02:12.535: Completing action FPI_DEVICE_ACTION_LIST in idle! 313s (process:2466): libfprint-device-DEBUG: 05:02:12.535: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.535: Got a new connection! 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.535: Got instructions of length 5 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.535: Received command CONT 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.535: Processing command CONT 313s (process:2466): libfprint-device-DEBUG: 05:02:12.535: Device reported deletion completion 313s (process:2466): libfprint-device-DEBUG: 05:02:12.535: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 313s (process:2466): libfprint-device-DEBUG: 05:02:12.535: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.536: Got a new connection! 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.536: Got instructions of length 16 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.536: Received command SET_KEEP_ALIVE 0 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.536: Keep alive toggled: 0 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.536: Got a new connection! 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.536: Got instructions of length 19 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.536: Received command SET_ENROLL_STAGES 5 313s (process:2466): libfprint-device-DEBUG: 05:02:12.536: Device reported close completion 313s (process:2466): libfprint-device-DEBUG: 05:02:12.536: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 313s (process:2466): libfprint-device-DEBUG: 05:02:12.536: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 313s ok 313s test_list_populated (__main__.VirtualDeviceStorage.test_list_populated) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.536: 90455055: ../libfprint/drivers/virtual-device.c:387 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.536: 90455084: ../libfprint/drivers/virtual-device-listener.c:153 313s (process:2466): libfprint-device-DEBUG: 05:02:12.537: Device reported open completion 313s (process:2466): libfprint-device-DEBUG: 05:02:12.537: Completing action FPI_DEVICE_ACTION_OPEN in idle! 313s (process:2466): libfprint-device-DEBUG: 05:02:12.537: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.537: Got a new connection! 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.537: Got instructions of length 9 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.537: Received command INSERT p1 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.537: Got a new connection! 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.537: Got instructions of length 7 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.537: Received command SCAN p2 313s (process:2466): libfprint-device-DEBUG: 05:02:12.537: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.537: Processing command INSERT p1 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.537: Processing command SCAN p2 313s (process:2466): libfprint-device-DEBUG: 05:02:12.537: Device reported finger status change: FP_FINGER_STATUS_NEEDED 313s (process:2466): libfprint-device-DEBUG: 05:02:12.537: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 313s (process:2466): libfprint-device-DEBUG: 05:02:12.537: Device reported finger status change: FP_FINGER_STATUS_NEEDED 313s (process:2466): libfprint-device-DEBUG: 05:02:12.537: Device reported enroll progress, reported 1 of 5 have been completed 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.537: Sleeping completed 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.538: Got a new connection! 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.538: Got instructions of length 7 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.538: Received command SCAN p2 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.538: Processing command SCAN p2 313s (process:2466): libfprint-device-DEBUG: 05:02:12.538: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 313s (process:2466): libfprint-device-DEBUG: 05:02:12.538: Device reported finger status change: FP_FINGER_STATUS_NEEDED 313s (process:2466): libfprint-device-DEBUG: 05:02:12.538: Device reported enroll progress, reported 2 of 5 have been completed 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.538: Sleeping completed 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.538: Got a new connection! 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.538: Got instructions of length 7 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.538: Received command SCAN p2 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.538: Processing command SCAN p2 313s (process:2466): libfprint-device-DEBUG: 05:02:12.538: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 313s (process:2466): libfprint-device-DEBUG: 05:02:12.538: Device reported finger status change: FP_FINGER_STATUS_NEEDED 313s (process:2466): libfprint-device-DEBUG: 05:02:12.538: Device reported enroll progress, reported 3 of 5 have been completed 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.538: Sleeping completed 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.538: Got a new connection! 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.538: Got instructions of length 7 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.538: Received command SCAN p2 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.538: Processing command SCAN p2 313s (process:2466): libfprint-device-DEBUG: 05:02:12.538: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 313s (process:2466): libfprint-device-DEBUG: 05:02:12.538: Device reported finger status change: FP_FINGER_STATUS_NEEDED 313s (process:2466): libfprint-device-DEBUG: 05:02:12.538: Device reported enroll progress, reported 4 of 5 have been completed 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.538: Sleeping completed 313s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:12.539: Got a new connection! 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.539: Got instructions of length 7 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.539: Received command SCAN p2 313s (process:2466): libfprint-virtual_device-DEBUG: 05:02:12.539: Processing command SCAN p2 313s (process:2466): libfprint-device-DEBUG: 05:02:12.539: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 313s (process:2466): libfprint-device-DEBUG: 05:02:12.539: Device reported finger status change: FP_FINGER_STATUS_NEEDED 313s (process:2466): libfprint-device-DEBUG: 05:02:12.539: Device reported enroll progress, reported 5 of 5 have been completed 313s (process:2466): libfprint-device-DEBUG: 05:02:12.539: Device reported enroll completion 313s (process:2466): libfprint-device-DEBUG: 05:02:12.539: Device reported finger status change: FP_FINGER_STATUS_NONE 313s (process:2466): libfprint-device-DEBUG: 05:02:12.539: Print for finger FP_FINGER_LEFT_LITTLE enrolled 313s (process:2466): libfprint-device-DEBUG: 05:02:12.539: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 313s (process:2466): libfprint-device-DEBUG: 05:02:12.539: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-device-DEBUG: 05:02:13.040: Device reported listing completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.040: Completing action FPI_DEVICE_ACTION_LIST in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.040: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.040: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.040: Got instructions of length 5 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.040: Received command CONT 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.040: Processing command CONT 314s (process:2466): libfprint-device-DEBUG: 05:02:13.040: Device reported deletion completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.040: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.040: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.041: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.041: Got instructions of length 16 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.041: Received command SET_KEEP_ALIVE 0 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.041: Keep alive toggled: 0 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.041: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.041: Got instructions of length 19 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.041: Received command SET_ENROLL_STAGES 5 314s (process:2466): libfprint-device-DEBUG: 05:02:13.041: Device reported close completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.041: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.041: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s Enroll done 314s ok 314s test_open_error (__main__.VirtualDeviceStorage.test_open_error) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.041: 90959967: ../libfprint/drivers/virtual-device.c:387 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.041: 90959984: ../libfprint/drivers/virtual-device-listener.c:153 314s (process:2466): libfprint-device-DEBUG: 05:02:13.041: Device reported open completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.042: Completing action FPI_DEVICE_ACTION_OPEN in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.042: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.042: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.042: Got instructions of length 16 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.042: Received command IGNORED_COMMAND 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.042: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.042: Got instructions of length 7 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.042: Received command ERROR 5 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.042: Processing command IGNORED_COMMAND 314s (process:2466): libfprint-device-DEBUG: 05:02:13.042: Device reported close completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.042: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.042: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.043: 90961179: ../libfprint/drivers/virtual-device.c:387 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.043: Processing command ERROR 5 314s (process:2466): libfprint-device-DEBUG: 05:02:13.043: Device reported open completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.043: Completing action FPI_DEVICE_ACTION_OPEN in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.043: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s ok 314s test_open_error_with_keep_alive (__main__.VirtualDeviceStorage.test_open_error_with_keep_alive) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.043: 90961464: ../libfprint/drivers/virtual-device.c:387 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.043: 90961482: ../libfprint/drivers/virtual-device-listener.c:153 314s (process:2466): libfprint-device-DEBUG: 05:02:13.043: Device reported open completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.043: Completing action FPI_DEVICE_ACTION_OPEN in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.043: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.043: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.043: Got instructions of length 16 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.043: Received command SET_KEEP_ALIVE 1 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.043: Keep alive toggled: 1 314s (process:2466): libfprint-device-DEBUG: 05:02:13.043: Device reported close completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.043: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.043: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.044: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.044: Got instructions of length 7 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.044: Received command ERROR 5 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.044: 90962424: ../libfprint/drivers/virtual-device.c:387 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.044: Processing command ERROR 5 314s (process:2466): libfprint-device-DEBUG: 05:02:13.044: Device reported open completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.044: Completing action FPI_DEVICE_ACTION_OPEN in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.044: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s ok 314s test_quick_enroll (__main__.VirtualDeviceStorage.test_quick_enroll) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.044: 90962660: ../libfprint/drivers/virtual-device.c:387 314s (process:2466): libfprint-device-DEBUG: 05:02:13.044: Device reported open completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.044: Completing action FPI_DEVICE_ACTION_OPEN in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.044: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.044: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.044: Got instructions of length 19 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.044: Received command SET_ENROLL_STAGES 1 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.045: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.045: Got instructions of length 14 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.045: Received command SCAN testprint 314s (process:2466): libfprint-device-DEBUG: 05:02:13.045: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.045: Processing command SCAN testprint 314s (process:2466): libfprint-device-DEBUG: 05:02:13.045: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2466): libfprint-device-DEBUG: 05:02:13.045: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2466): libfprint-device-DEBUG: 05:02:13.045: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2466): libfprint-device-DEBUG: 05:02:13.045: Device reported enroll progress, reported 1 of 1 have been completed 314s (process:2466): libfprint-device-DEBUG: 05:02:13.045: Device reported enroll completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.045: Device reported finger status change: FP_FINGER_STATUS_NONE 314s (process:2466): libfprint-device-DEBUG: 05:02:13.045: Print for finger FP_FINGER_LEFT_LITTLE enrolled 314s (process:2466): libfprint-device-DEBUG: 05:02:13.045: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.045: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.045: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.045: Got instructions of length 5 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.045: Received command CONT 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.045: Processing command CONT 314s (process:2466): libfprint-device-DEBUG: 05:02:13.045: Device reported deletion completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.045: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.045: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.045: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.046: Got instructions of length 16 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.046: Received command SET_KEEP_ALIVE 0 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.046: Keep alive toggled: 0 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.046: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.046: Got instructions of length 19 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.046: Received command SET_ENROLL_STAGES 5 314s (process:2466): libfprint-device-DEBUG: 05:02:13.046: Device reported close completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.046: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.046: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s Enroll done 314s ok 314s test_verify_missing_print (__main__.VirtualDeviceStorage.test_verify_missing_print) ... (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.046: 90964601: ../libfprint/drivers/virtual-device.c:387 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.046: 90964616: ../libfprint/drivers/virtual-device-listener.c:153 314s (process:2466): libfprint-device-DEBUG: 05:02:13.046: Device reported open completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.046: Completing action FPI_DEVICE_ACTION_OPEN in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.046: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.046: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.046: Got instructions of length 23 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.046: Received command SCAN not-existing-print 314s (process:2466): libfprint-device-DEBUG: 05:02:13.046: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.047: Processing command SCAN not-existing-print 314s (process:2466): libfprint-device-DEBUG: 05:02:13.047: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2466): libfprint-device-DEBUG: 05:02:13.047: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.047: Virtual device scanned print not-existing-print 314s (process:2466): libfprint-device-DEBUG: 05:02:13.047: Device reported verify result 314s (process:2466): libfprint-device-DEBUG: 05:02:13.047: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2466): libfprint-device-DEBUG: 05:02:13.047: Device reported verify completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.047: Device reported finger status change: FP_FINGER_STATUS_NONE 314s (process:2466): libfprint-device-DEBUG: 05:02:13.047: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.047: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.047: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.047: Got instructions of length 5 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.047: Received command CONT 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.047: Processing command CONT 314s (process:2466): libfprint-device-DEBUG: 05:02:13.047: Device reported deletion completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.047: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.047: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.047: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.047: Got instructions of length 16 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.047: Received command SET_KEEP_ALIVE 0 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.047: Keep alive toggled: 0 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.047: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.047: Got instructions of length 19 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.047: Received command SET_ENROLL_STAGES 5 314s (process:2466): libfprint-device-DEBUG: 05:02:13.047: Device reported close completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.047: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.047: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s ok 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.048: 90966406: ../libfprint/drivers/virtual-device.c:752 314s test_device_unplug (__main__.VirtualDeviceUnplugging.test_device_unplug) ... (process:2466): libfprint-context-DEBUG: 05:02:13.048: Initializing FpContext (libfprint version 1.94.9+tod1) 314s (process:2466): libfprint-tod-DEBUG: 05:02:13.048: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 314s (process:2466): libfprint-context-DEBUG: 05:02:13.050: No driver found for USB device 1D6B:0003 314s (process:2466): libfprint-context-DEBUG: 05:02:13.050: No driver found for USB device 0627:0001 314s (process:2466): libfprint-context-DEBUG: 05:02:13.050: No driver found for USB device 1D6B:0002 314s (process:2466): libfprint-context-DEBUG: 05:02:13.050: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-nqds2qwv/virtual-device.socket 314s (process:2466): libfprint-context-DEBUG: 05:02:13.050: created 314s (process:2466): libfprint-context-DEBUG: 05:02:13.050: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-u8jqzv12/virtual-device-storage.socket 314s (process:2466): libfprint-context-DEBUG: 05:02:13.051: created 314s (process:2466): libfprint-device-DEBUG: 05:02:13.051: Device reported probe completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.051: Device reported probe completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.051: Completing action FPI_DEVICE_ACTION_PROBE in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.051: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 314s (process:2466): libfprint-device-DEBUG: 05:02:13.051: Completing action FPI_DEVICE_ACTION_PROBE in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.051: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.051: 90969987: ../libfprint/drivers/virtual-device.c:387 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.051: 90970040: ../libfprint/drivers/virtual-device-listener.c:153 314s (process:2466): libfprint-device-DEBUG: 05:02:13.051: Device reported open completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.051: Completing action FPI_DEVICE_ACTION_OPEN in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.051: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.052: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.052: Got instructions of length 7 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.052: Received command UNPLUG 314s (process:2466): libfprint-device-DEBUG: 05:02:13.052: Device reported close completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.052: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.052: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.052: 90970953: ../libfprint/drivers/virtual-device.c:752 314s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:13.052: 90970986: ../libfprint/drivers/virtual-device-storage.c:253 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.052: 90970993: ../libfprint/drivers/virtual-device.c:752 314s ok 314s test_device_unplug_during_verify (__main__.VirtualDeviceUnplugging.test_device_unplug_during_verify) ... (process:2466): libfprint-context-DEBUG: 05:02:13.053: Initializing FpContext (libfprint version 1.94.9+tod1) 314s (process:2466): libfprint-tod-DEBUG: 05:02:13.053: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 314s (process:2466): libfprint-context-DEBUG: 05:02:13.055: No driver found for USB device 1D6B:0003 314s (process:2466): libfprint-context-DEBUG: 05:02:13.055: No driver found for USB device 0627:0001 314s (process:2466): libfprint-context-DEBUG: 05:02:13.055: No driver found for USB device 1D6B:0002 314s (process:2466): libfprint-context-DEBUG: 05:02:13.055: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-nqds2qwv/virtual-device.socket 314s (process:2466): libfprint-context-DEBUG: 05:02:13.055: created 314s (process:2466): libfprint-context-DEBUG: 05:02:13.055: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-u8jqzv12/virtual-device-storage.socket 314s (process:2466): libfprint-context-DEBUG: 05:02:13.055: created 314s (process:2466): libfprint-device-DEBUG: 05:02:13.056: Device reported probe completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.056: Device reported probe completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.056: Completing action FPI_DEVICE_ACTION_PROBE in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.056: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 314s (process:2466): libfprint-device-DEBUG: 05:02:13.056: Completing action FPI_DEVICE_ACTION_PROBE in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.056: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.056: 90974512: ../libfprint/drivers/virtual-device.c:387 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.056: 90974532: ../libfprint/drivers/virtual-device-listener.c:153 314s (process:2466): libfprint-device-DEBUG: 05:02:13.056: Device reported open completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.056: Completing action FPI_DEVICE_ACTION_OPEN in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.056: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 314s (process:2466): libfprint-device-DEBUG: 05:02:13.056: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 314s (process:2466): libfprint-device-DEBUG: 05:02:13.056: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2466): libfprint-virtual_device_connection-DEBUG: 05:02:13.056: Got a new connection! 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.056: Got instructions of length 7 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.056: Received command UNPLUG 314s (process:2466): libfprint-device-DEBUG: 05:02:13.156: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-device-DEBUG: 05:02:13.557: Device reported generic error (No commands arrived in time to run!) during action; action was: FPI_DEVICE_ACTION_VERIFY 314s (process:2466): libfprint-device-DEBUG: 05:02:13.557: Device reported verify completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.557: Device reported finger status change: FP_FINGER_STATUS_NONE 314s (process:2466): libfprint-device-DEBUG: 05:02:13.557: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.557: Updated temperature model after 0.40 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-device-DEBUG: 05:02:13.558: Device reported close completion 314s (process:2466): libfprint-device-DEBUG: 05:02:13.558: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 314s (process:2466): libfprint-device-DEBUG: 05:02:13.558: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.558: 91476460: ../libfprint/drivers/virtual-device.c:752 314s (process:2466): libfprint-virtual_device_storage-DEBUG: 05:02:13.558: 91476511: ../libfprint/drivers/virtual-device-storage.c:253 314s (process:2466): libfprint-virtual_device-DEBUG: 05:02:13.558: 91476523: ../libfprint/drivers/virtual-device.c:752 314s ok 314s 314s ---------------------------------------------------------------------- 314s Ran 86 tests in 17.752s 314s 314s OK (skipped=1) 314s PASS: libfprint-2/virtual-device.test 314s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 314s TAP version 14 314s # random seed: R02S0824df4741af5bf9d5801401e4896b83 314s 1..4 314s # Start of context tests 314s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 314s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 314s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf94504ff2660, GType is 201068880468608 314s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 314s ok 1 /context/new 314s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 314s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 314s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 314s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 314s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 314s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 314s ok 2 /context/no-devices 314s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 314s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 314s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf94504ff2660, GType is 201068880468608 314s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 314s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 314s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 314s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 314s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 314s # libfprint-context-DEBUG: created 314s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 314s # 314s # libfprint-device-DEBUG: Device reported probe completion 314s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 314s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 314s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 314s # 314s # libfprint-device-DEBUG: Device reported open completion 314s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 314s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 314s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 314s # 314s # libfprint-device-DEBUG: Device reported close completion 314s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 314s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 314s ok 3 /context/has-virtual-device 314s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 314s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 314s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xf94504ff2660, GType is 201068880468608 314s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 314s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 314s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 314s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 314s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 314s # libfprint-context-DEBUG: created 314s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 314s # 314s # libfprint-device-DEBUG: Device reported probe completion 314s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 314s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 314s ok 4 /context/enumerates-new-devices 314s # End of context tests 314s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test 314s Running test: libfprint-2/driver-goodixmoc.test 314s ** (umockdev-run:2496): DEBUG: 05:02:13.674: umockdev.vala:127: Created udev test bed /tmp/umockdev.IX1312 314s ** (umockdev-run:2496): DEBUG: 05:02:13.674: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-9 314s ** (umockdev-run:2496): DEBUG: 05:02:13.675: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-9 (subsystem usb) 314s ** (umockdev-run:2496): DEBUG: 05:02:13.678: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IX1312/dev/bus/usb/003/004 314s ** (umockdev-run:2496): DEBUG: 05:02:13.678: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3 314s ** (umockdev-run:2496): DEBUG: 05:02:13.679: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb) 314s ** (umockdev-run:2496): DEBUG: 05:02:13.681: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IX1312/dev/bus/usb/003/001 314s ** (umockdev-run:2496): DEBUG: 05:02:13.681: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 314s ** (umockdev-run:2496): DEBUG: 05:02:13.682: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 314s (process:2500): libfprint-context-DEBUG: 05:02:13.784: Initializing FpContext (libfprint version 1.94.9+tod1) 314s (process:2500): libfprint-tod-DEBUG: 05:02:13.784: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 314s (process:2500): libfprint-context-DEBUG: 05:02:13.786: No driver found for USB device 1D6B:0002 314s (process:2500): libfprint-device-DEBUG: 05:02:13.788: Device reported probe completion 314s (process:2500): libfprint-device-DEBUG: 05:02:13.788: Completing action FPI_DEVICE_ACTION_PROBE in idle! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.788: Not updating temperature model, device can run continuously! 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.790: [goodixmoc] FP_INIT_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.790: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.791: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.792: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.792: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.793: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-goodixmoc-DEBUG: 05:02:13.793: Firmware type: APP 314s (process:2500): libfprint-goodixmoc-DEBUG: 05:02:13.793: Firmware version: 01000274 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.793: [goodixmoc] FP_INIT_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.793: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.794: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.794: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.794: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.795: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.796: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.796: [goodixmoc] FP_INIT_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.796: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.797: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.797: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.797: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.798: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.799: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.799: [goodixmoc] FP_INIT_NUM_STATES completed successfully 314s (process:2500): libfprint-device-DEBUG: 05:02:13.799: Device reported open completion 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.799: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-device-DEBUG: 05:02:13.799: Completing action FPI_DEVICE_ACTION_OPEN in idle! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.799: Not updating temperature model, device can run continuously! 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.799: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.800: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.801: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.801: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.802: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-goodixmoc-DEBUG: 05:02:13.802: Successfully cleared storage 314s (process:2500): libfprint-device-DEBUG: 05:02:13.802: Device reported deletion completion 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.802: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-device-DEBUG: 05:02:13.802: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.802: Not updating temperature model, device can run continuously! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.803: Not updating temperature model, device can run continuously! 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.803: [goodixmoc] enroll entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.803: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.804: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.804: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.805: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.806: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.806: [goodixmoc] enroll entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.806: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.807: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.807: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.807: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.808: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.809: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.809: [goodixmoc] enroll entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.809: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.810: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.810: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.810: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.811: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.812: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.813: [goodixmoc] enroll entering state 3 314s (process:2500): libfprint-device-DEBUG: 05:02:13.813: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.813: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.813: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.813: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.814: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.815: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.815: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.816: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.816: [goodixmoc] enroll entering state 4 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.816: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.816: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.817: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.817: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.818: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.818: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.819: Device reported enroll progress, reported 1 of 12 have been completed 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.819: [goodixmoc] enroll entering state 5 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.819: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.819: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.820: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.820: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.821: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.821: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.822: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.822: [goodixmoc] enroll entering state 3 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.822: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.822: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.822: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.823: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.823: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.824: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.825: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.825: [goodixmoc] enroll entering state 4 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.825: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.825: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.825: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.826: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.826: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.827: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.828: Device reported enroll progress, reported 2 of 12 have been completed 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.828: [goodixmoc] enroll entering state 5 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.828: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.828: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.828: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.829: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.829: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.830: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.830: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.830: [goodixmoc] enroll entering state 3 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.830: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.831: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.831: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.831: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.832: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.833: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.833: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.833: [goodixmoc] enroll entering state 4 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.833: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.833: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.834: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.834: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.835: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.835: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.836: Device reported enroll progress, reported 3 of 12 have been completed 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.836: [goodixmoc] enroll entering state 5 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.836: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.836: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.837: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.837: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.838: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.838: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.839: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.839: [goodixmoc] enroll entering state 3 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.839: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.839: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.839: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.840: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.840: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.841: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.842: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.842: [goodixmoc] enroll entering state 4 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.842: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.842: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.842: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.843: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.844: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.844: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.845: Device reported enroll progress, reported 4 of 12 have been completed 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.845: [goodixmoc] enroll entering state 5 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.845: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.845: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.845: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.846: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.847: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.847: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.848: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.848: [goodixmoc] enroll entering state 3 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.848: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.848: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.848: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.849: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.849: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.850: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.850: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.850: [goodixmoc] enroll entering state 4 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.850: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.851: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.851: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.851: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.852: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.852: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.853: Device reported enroll progress, reported 5 of 12 have been completed 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.853: [goodixmoc] enroll entering state 5 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.853: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.853: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.854: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.854: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.855: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.855: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.856: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.856: [goodixmoc] enroll entering state 3 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.856: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.856: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.857: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.857: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.858: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.858: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.859: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.859: [goodixmoc] enroll entering state 4 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.859: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.860: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.860: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.860: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.861: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.861: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.862: Device reported enroll progress, reported 6 of 12 have been completed 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.862: [goodixmoc] enroll entering state 5 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.862: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.862: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.863: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.863: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.864: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.865: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.865: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.865: [goodixmoc] enroll entering state 3 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.865: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.865: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.866: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.866: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.867: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.867: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.868: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.868: [goodixmoc] enroll entering state 4 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.868: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.868: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.869: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.869: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.870: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.870: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.871: Device reported enroll progress, reported 7 of 12 have been completed 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.871: [goodixmoc] enroll entering state 5 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.871: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.872: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.872: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.872: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.873: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.874: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.874: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.874: [goodixmoc] enroll entering state 3 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.874: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.875: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.875: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.876: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.876: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.877: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.877: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.877: [goodixmoc] enroll entering state 4 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.877: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.878: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.878: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.879: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.879: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.880: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.880: Device reported enroll progress, reported 8 of 12 have been completed 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.880: [goodixmoc] enroll entering state 5 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.880: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.881: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.881: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.881: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.882: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.882: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.883: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.883: [goodixmoc] enroll entering state 3 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.883: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.883: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.884: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.884: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.885: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.886: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.886: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.886: [goodixmoc] enroll entering state 4 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.886: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.887: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.887: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.887: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.888: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.889: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.889: Device reported enroll progress, reported 9 of 12 have been completed 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.889: [goodixmoc] enroll entering state 5 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.889: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.890: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.890: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.891: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.891: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.892: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.893: [goodixmoc] enroll entering state 3 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.893: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.893: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.893: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.894: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.894: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.895: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.895: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.895: [goodixmoc] enroll entering state 4 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.895: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.896: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.896: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.896: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.897: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.897: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.898: Device reported enroll progress, reported 10 of 12 have been completed 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.898: [goodixmoc] enroll entering state 5 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.898: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.899: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.899: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.899: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.900: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.900: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.901: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.901: [goodixmoc] enroll entering state 3 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.901: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.901: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.902: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.902: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.903: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.903: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.904: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.904: [goodixmoc] enroll entering state 4 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.904: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.904: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.904: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.905: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.905: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.906: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.907: Device reported enroll progress, reported 11 of 12 have been completed 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.907: [goodixmoc] enroll entering state 5 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.907: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.907: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.907: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.908: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.908: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.909: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.910: [goodixmoc] enroll entering state 3 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.910: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.910: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.910: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.911: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.912: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.912: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.913: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.913: [goodixmoc] enroll entering state 4 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.913: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.913: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.914: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.914: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.915: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.916: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.916: Device reported enroll progress, reported 12 of 12 have been completed 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.916: [goodixmoc] enroll entering state 6 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.917: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.917: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.917: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.918: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.918: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.919: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.919: [goodixmoc] enroll entering state 7 314s (process:2500): libfprint-goodixmoc-DEBUG: 05:02:13.919: user_id: FP1-00000000-0-00000000-nobody, user_id_len: 30, finger: 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.919: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.920: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.920: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.920: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.921: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.921: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.922: [goodixmoc] enroll entering state 8 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.922: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.922: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.922: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.923: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.923: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.924: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.925: [goodixmoc] enroll completed successfully 314s (process:2500): libfprint-goodixmoc-DEBUG: 05:02:13.925: Enrollment complete! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.925: Device reported enroll completion 314s (process:2500): libfprint-device-DEBUG: 05:02:13.925: Device reported finger status change: FP_FINGER_STATUS_NONE 314s (process:2500): libfprint-device-DEBUG: 05:02:13.925: Print for finger FP_FINGER_UNKNOWN enrolled 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.925: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-device-DEBUG: 05:02:13.925: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.925: Not updating temperature model, device can run continuously! 314s (process:2500): libfprint-goodixmoc-DEBUG: 05:02:13.925: 91843456: ../libfprint/drivers/goodixmoc/goodix.c:1556 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.925: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.925: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.926: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.926: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.927: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-goodixmoc-DEBUG: 05:02:13.927: Query complete! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.927: Device reported listing completion 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.928: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-device-DEBUG: 05:02:13.928: Completing action FPI_DEVICE_ACTION_LIST in idle! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.928: Not updating temperature model, device can run continuously! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.928: Not updating temperature model, device can run continuously! 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.928: [goodixmoc] verify entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.928: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.929: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.930: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.930: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.931: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.931: [goodixmoc] verify entering state 1 314s (process:2500): libfprint-device-DEBUG: 05:02:13.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.931: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.932: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.932: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.932: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.933: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.933: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.934: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.934: [goodixmoc] verify entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.934: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.934: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.934: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.935: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.935: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.936: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-DEBUG: 05:02:13.936: match, score: 28, study: 0 314s (process:2500): libfprint-device-DEBUG: 05:02:13.937: Device reported verify result 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.937: [goodixmoc] verify entering state 3 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.937: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.937: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.937: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.938: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.938: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.939: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.940: [goodixmoc] verify completed successfully 314s (process:2500): libfprint-goodixmoc-DEBUG: 05:02:13.940: Verify complete! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.940: Device reported verify completion 314s (process:2500): libfprint-device-DEBUG: 05:02:13.940: Device reported finger status change: FP_FINGER_STATUS_NONE 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.940: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-device-DEBUG: 05:02:13.940: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.940: Not updating temperature model, device can run continuously! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.940: Not updating temperature model, device can run continuously! 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.940: [goodixmoc] verify entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.940: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.941: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.942: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.942: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.943: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.944: [goodixmoc] verify entering state 1 314s (process:2500): libfprint-device-DEBUG: 05:02:13.944: Device reported finger status change: FP_FINGER_STATUS_NEEDED 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.944: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.944: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.944: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.945: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.946: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.946: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-device-DEBUG: 05:02:13.947: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.947: [goodixmoc] verify entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.947: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.947: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.948: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.948: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.949: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.949: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-DEBUG: 05:02:13.950: match, score: 35, study: 0 314s (process:2500): libfprint-device-DEBUG: 05:02:13.950: Device reported identify result 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.950: [goodixmoc] verify entering state 3 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.950: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.950: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.951: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.951: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.952: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.953: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.953: [goodixmoc] verify completed successfully 314s (process:2500): libfprint-goodixmoc-DEBUG: 05:02:13.953: Verify complete! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.953: Device reported identify completion 314s (process:2500): libfprint-device-DEBUG: 05:02:13.953: Device reported finger status change: FP_FINGER_STATUS_NONE 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.953: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-device-DEBUG: 05:02:13.954: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.954: Not updating temperature model, device can run continuously! 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.954: [goodixmoc] FP_CMD_NUM_STATES entering state 0 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.955: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.955: [goodixmoc] FP_CMD_NUM_STATES entering state 1 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.956: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.956: [goodixmoc] FP_CMD_NUM_STATES entering state 2 314s (process:2500): libfprint-goodixmoc-DEBUG: 05:02:13.957: Successfully deleted enrolled user 314s (process:2500): libfprint-device-DEBUG: 05:02:13.957: Device reported deletion completion 314s (process:2500): libfprint-SSM-DEBUG: 05:02:13.957: [goodixmoc] FP_CMD_NUM_STATES completed successfully 314s (process:2500): libfprint-device-DEBUG: 05:02:13.957: Completing action FPI_DEVICE_ACTION_DELETE in idle! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.957: Not updating temperature model, device can run continuously! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.957: Device reported close completion 314s (process:2500): libfprint-device-DEBUG: 05:02:13.957: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 314s (process:2500): libfprint-device-DEBUG: 05:02:13.957: Not updating temperature model, device can run continuously! 314s enrolling 314s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfec094dab100 (FpiDeviceGoodixMoc at 0x3bf95b90)>, 1, None, None, None) 314s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfec094dab100 (FpiDeviceGoodixMoc at 0x3bf95b90)>, 2, None, None, None) 314s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfec094dab100 (FpiDeviceGoodixMoc at 0x3bf95b90)>, 3, None, None, None) 314s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfec094dab100 (FpiDeviceGoodixMoc at 0x3bf95b90)>, 4, None, None, None) 314s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfec094dab100 (FpiDeviceGoodixMoc at 0x3bf95b90)>, 5, None, None, None) 314s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfec094dab100 (FpiDeviceGoodixMoc at 0x3bf95b90)>, 6, None, None, None) 314s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfec094dab100 (FpiDeviceGoodixMoc at 0x3bf95b90)>, 7, None, None, None) 314s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfec094dab100 (FpiDeviceGoodixMoc at 0x3bf95b90)>, 8, None, None, None) 314s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfec094dab100 (FpiDeviceGoodixMoc at 0x3bf95b90)>, 9, None, None, None) 314s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfec094dab100 (FpiDeviceGoodixMoc at 0x3bf95b90)>, 10, None, None, None) 314s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfec094dab100 (FpiDeviceGoodixMoc at 0x3bf95b90)>, 11, None, None, None) 314s enroll progress: (<__gi__.FpiDeviceGoodixMoc object at 0xfec094dab100 (FpiDeviceGoodixMoc at 0x3bf95b90)>, 12, None, None, None) 314s enroll done 314s listing 314s listing done 314s verifying 314s verify done 314s async identifying 314s indentification_done: 314s deleting 314s delete done 315s ** (umockdev-run:2496): DEBUG: 05:02:13.988: umockdev.vala:154: Removing test bed /tmp/umockdev.IX1312 315s (umockdev-run:2496): GLib-DEBUG: 05:02:13.992: unsetenv() is not thread-safe and should not be used after threads are created 315s PASS: libfprint-2/driver-goodixmoc.test 315s Running test: libfprint-2/driver-realtek-5816.test 315s ** (umockdev-run:2508): DEBUG: 05:02:14.053: umockdev.vala:127: Created udev test bed /tmp/umockdev.X14C22 315s ** (umockdev-run:2508): DEBUG: 05:02:14.053: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-6 315s ** (umockdev-run:2508): DEBUG: 05:02:14.055: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-6 (subsystem usb) 315s ** (umockdev-run:2508): DEBUG: 05:02:14.057: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.X14C22/dev/bus/usb/001/006 315s ** (umockdev-run:2508): DEBUG: 05:02:14.057: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 315s ** (umockdev-run:2508): DEBUG: 05:02:14.058: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 315s ** (umockdev-run:2508): DEBUG: 05:02:14.061: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.X14C22/dev/bus/usb/001/001 315s ** (umockdev-run:2508): DEBUG: 05:02:14.061: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 315s ** (umockdev-run:2508): DEBUG: 05:02:14.061: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 315s Executing: libfprint-2/driver-realtek-5816.test 315s (process:2512): libfprint-context-DEBUG: 05:02:14.168: Initializing FpContext (libfprint version 1.94.9+tod1) 315s (process:2512): libfprint-tod-DEBUG: 05:02:14.168: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 315s (process:2512): libfprint-context-DEBUG: 05:02:14.170: No driver found for USB device 1D6B:0002 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.171: 92089565: ../libfprint/drivers/realtek/realtek.c:1224 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.174: Device name: Realtek USB2.0 Finger Print Bridge 315s (process:2512): libfprint-device-DEBUG: 05:02:14.175: Device reported probe completion 315s (process:2512): libfprint-device-DEBUG: 05:02:14.175: Completing action FPI_DEVICE_ACTION_PROBE in idle! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.175: Not updating temperature model, device can run continuously! 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.176: 92095026: ../libfprint/drivers/realtek/realtek.c:1269 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.177: [realtek] Init entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.177: [realtek] Init entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.178: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.178: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.178: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.179: [realtek] Init entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.179: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.179: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.179: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.180: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.181: [realtek] Init completed successfully 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.181: Init complete! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.181: Device reported open completion 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.181: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-device-DEBUG: 05:02:14.181: Completing action FPI_DEVICE_ACTION_OPEN in idle! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.181: Not updating temperature model, device can run continuously! 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.181: 92099600: ../libfprint/drivers/realtek/realtek.c:1332 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.181: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.182: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.182: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.182: Successfully cleared storage 315s (process:2512): libfprint-device-DEBUG: 05:02:14.182: Device reported deletion completion 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.182: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-device-DEBUG: 05:02:14.182: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.182: Not updating temperature model, device can run continuously! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.183: Not updating temperature model, device can run continuously! 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.183: 92101795: ../libfprint/drivers/realtek/realtek.c:1201 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.183: [realtek] Enroll entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.183: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.184: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.184: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.185: [realtek] Enroll entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.185: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.185: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.186: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.186: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.186: [realtek] Enroll entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.186: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.187: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.187: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.187: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.188: [realtek] Enroll entering state 3 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.188: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.188: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.188: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.189: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.190: Device reported finger status change: FP_FINGER_STATUS_PRESENT 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.190: [realtek] Enroll entering state 4 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.190: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.190: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.190: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.191: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.192: Device reported finger status change: FP_FINGER_STATUS_NONE 315s (process:2512): libfprint-device-DEBUG: 05:02:14.192: Device reported enroll progress, reported 1 of 8 have been completed 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.192: [realtek] Enroll entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.192: Device reported finger status change: FP_FINGER_STATUS_NEEDED 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.192: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.192: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.193: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.193: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.193: [realtek] Enroll entering state 3 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.193: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.194: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.194: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.195: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.195: Device reported finger status change: FP_FINGER_STATUS_PRESENT 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.195: [realtek] Enroll entering state 4 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.195: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.196: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.196: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.197: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.198: Device reported finger status change: FP_FINGER_STATUS_NONE 315s (process:2512): libfprint-device-DEBUG: 05:02:14.198: Device reported enroll progress, reported 2 of 8 have been completed 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.198: [realtek] Enroll entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.198: Device reported finger status change: FP_FINGER_STATUS_NEEDED 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.198: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.198: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.198: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.198: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.199: [realtek] Enroll entering state 3 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.199: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.199: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.200: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.200: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.201: Device reported finger status change: FP_FINGER_STATUS_PRESENT 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.201: [realtek] Enroll entering state 4 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.201: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.201: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.201: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.202: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.202: Device reported finger status change: FP_FINGER_STATUS_NONE 315s (process:2512): libfprint-device-DEBUG: 05:02:14.203: Device reported enroll progress, reported 3 of 8 have been completed 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.203: [realtek] Enroll entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.203: Device reported finger status change: FP_FINGER_STATUS_NEEDED 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.203: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.203: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.203: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.203: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.204: [realtek] Enroll entering state 3 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.204: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.204: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.204: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.205: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.205: Device reported finger status change: FP_FINGER_STATUS_PRESENT 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.206: [realtek] Enroll entering state 4 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.206: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.206: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.206: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.207: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.207: Device reported finger status change: FP_FINGER_STATUS_NONE 315s (process:2512): libfprint-device-DEBUG: 05:02:14.207: Device reported enroll progress, reported 4 of 8 have been completed 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.207: [realtek] Enroll entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.207: Device reported finger status change: FP_FINGER_STATUS_NEEDED 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.207: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.208: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.208: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.208: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.208: [realtek] Enroll entering state 3 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.208: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.209: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.209: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.210: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.210: Device reported finger status change: FP_FINGER_STATUS_PRESENT 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.210: [realtek] Enroll entering state 4 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.210: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.211: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.211: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.211: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.212: Device reported finger status change: FP_FINGER_STATUS_NONE 315s (process:2512): libfprint-device-DEBUG: 05:02:14.212: Device reported enroll progress, reported 5 of 8 have been completed 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.212: [realtek] Enroll entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.212: Device reported finger status change: FP_FINGER_STATUS_NEEDED 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.212: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.212: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.212: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.213: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.213: [realtek] Enroll entering state 3 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.213: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.213: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.214: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.214: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.215: Device reported finger status change: FP_FINGER_STATUS_PRESENT 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.215: [realtek] Enroll entering state 4 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.215: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.215: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.215: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.216: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.217: Device reported finger status change: FP_FINGER_STATUS_NONE 315s (process:2512): libfprint-device-DEBUG: 05:02:14.217: Device reported enroll progress, reported 6 of 8 have been completed 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.217: [realtek] Enroll entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.217: Device reported finger status change: FP_FINGER_STATUS_NEEDED 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.217: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.217: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.217: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.217: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.218: [realtek] Enroll entering state 3 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.218: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.218: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.219: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.219: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.220: Device reported finger status change: FP_FINGER_STATUS_PRESENT 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.220: [realtek] Enroll entering state 4 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.220: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.220: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.220: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.221: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.221: Device reported finger status change: FP_FINGER_STATUS_NONE 315s (process:2512): libfprint-device-DEBUG: 05:02:14.222: Device reported enroll progress, reported 7 of 8 have been completed 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.222: [realtek] Enroll entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.222: Device reported finger status change: FP_FINGER_STATUS_NEEDED 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.222: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.222: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.222: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.222: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.223: [realtek] Enroll entering state 3 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.223: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.223: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.224: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.224: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.225: Device reported finger status change: FP_FINGER_STATUS_PRESENT 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.225: [realtek] Enroll entering state 4 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.225: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.225: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.225: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.226: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.227: Device reported finger status change: FP_FINGER_STATUS_NONE 315s (process:2512): libfprint-device-DEBUG: 05:02:14.227: Device reported enroll progress, reported 8 of 8 have been completed 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.227: [realtek] Enroll entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.227: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.227: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.227: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.227: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.228: [realtek] Enroll entering state 3 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.228: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.228: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.228: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.229: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.230: Device reported finger status change: FP_FINGER_STATUS_PRESENT 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.230: [realtek] Enroll entering state 4 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.230: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.230: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.230: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.231: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.231: Device reported finger status change: FP_FINGER_STATUS_NONE 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.231: [realtek] Enroll entering state 5 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.231: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.232: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.232: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.233: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.233: [realtek] Enroll entering state 6 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.233: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.233: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.234: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.234: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.234: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.235: [realtek] Enroll completed successfully 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.235: Enrollment complete! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.235: Device reported enroll completion 315s (process:2512): libfprint-device-DEBUG: 05:02:14.235: Print for finger FP_FINGER_UNKNOWN enrolled 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.235: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-device-DEBUG: 05:02:14.235: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.235: Not updating temperature model, device can run continuously! 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.235: 92153728: ../libfprint/drivers/realtek/realtek.c:1344 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.235: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.236: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.236: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.237: Query templates complete! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.237: Device reported listing completion 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.237: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-device-DEBUG: 05:02:14.237: Completing action FPI_DEVICE_ACTION_LIST in idle! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.237: Not updating temperature model, device can run continuously! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.237: Not updating temperature model, device can run continuously! 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.237: 92155796: ../libfprint/drivers/realtek/realtek.c:1177 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.237: [realtek] Verify & Identify entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.237: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.238: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.239: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.239: [realtek] Verify & Identify entering state 1 315s (process:2512): libfprint-device-DEBUG: 05:02:14.239: Device reported finger status change: FP_FINGER_STATUS_NEEDED 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.239: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.240: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.240: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.240: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.240: [realtek] Verify & Identify entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.240: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.241: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.241: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.242: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.242: Device reported finger status change: FP_FINGER_STATUS_PRESENT 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.242: [realtek] Verify & Identify entering state 3 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.242: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.243: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.243: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.243: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.244: Device reported finger status change: FP_FINGER_STATUS_NONE 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.244: [realtek] Verify & Identify entering state 4 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.244: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.244: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.245: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.245: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.246: Device reported verify result 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.246: [realtek] Verify & Identify entering state 5 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.246: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.246: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.246: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.246: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.247: [realtek] Verify & Identify completed successfully 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.247: Verify complete! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.247: Device reported verify completion 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.247: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-device-DEBUG: 05:02:14.247: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.247: Not updating temperature model, device can run continuously! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.248: Not updating temperature model, device can run continuously! 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.248: 92166253: ../libfprint/drivers/realtek/realtek.c:1177 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.248: [realtek] Verify & Identify entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.248: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.248: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.249: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.249: [realtek] Verify & Identify entering state 1 315s (process:2512): libfprint-device-DEBUG: 05:02:14.250: Device reported finger status change: FP_FINGER_STATUS_NEEDED 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.250: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.250: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.250: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.250: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.251: [realtek] Verify & Identify entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.251: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.251: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.251: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.252: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.253: Device reported finger status change: FP_FINGER_STATUS_PRESENT 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.253: [realtek] Verify & Identify entering state 3 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.253: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.253: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.253: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.254: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.255: Device reported finger status change: FP_FINGER_STATUS_NONE 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.255: [realtek] Verify & Identify entering state 4 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.255: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.255: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.255: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.256: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-device-DEBUG: 05:02:14.256: Device reported identify result 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.256: [realtek] Verify & Identify completed successfully 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.256: Verify complete! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.257: Device reported identify completion 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.257: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-device-DEBUG: 05:02:14.257: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.257: Not updating temperature model, device can run continuously! 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.257: 92175690: ../libfprint/drivers/realtek/realtek.c:1313 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.257: [realtek] Delete print entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.257: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.258: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.258: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.259: [realtek] Delete print entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.259: [realtek] FP_RTK_CMD_NUM_STATES entering state 0 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.259: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.260: [realtek] FP_RTK_CMD_NUM_STATES entering state 1 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.260: [realtek] FP_RTK_CMD_NUM_STATES entering state 2 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.260: [realtek] Delete print completed successfully 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.260: Delete print complete! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.260: Device reported deletion completion 315s (process:2512): libfprint-SSM-DEBUG: 05:02:14.260: [realtek] FP_RTK_CMD_NUM_STATES completed successfully 315s (process:2512): libfprint-device-DEBUG: 05:02:14.260: Completing action FPI_DEVICE_ACTION_DELETE in idle! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.260: Not updating temperature model, device can run continuously! 315s (process:2512): libfprint-realtek-DEBUG: 05:02:14.260: 92178920: ../libfprint/drivers/realtek/realtek.c:1301 315s (process:2512): libfprint-device-DEBUG: 05:02:14.261: Device reported close completion 315s (process:2512): libfprint-device-DEBUG: 05:02:14.261: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 315s (process:2512): libfprint-device-DEBUG: 05:02:14.261: Not updating temperature model, device can run continuously! 315s enrolling 315s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf031f5b7e100 (FpiDeviceRealtek at 0x1ba6dce0)>, 1, None, None, None) 315s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf031f5b7e100 (FpiDeviceRealtek at 0x1ba6dce0)>, 2, None, None, None) 315s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf031f5b7e100 (FpiDeviceRealtek at 0x1ba6dce0)>, 3, None, None, None) 315s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf031f5b7e100 (FpiDeviceRealtek at 0x1ba6dce0)>, 4, None, None, None) 315s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf031f5b7e100 (FpiDeviceRealtek at 0x1ba6dce0)>, 5, None, None, None) 315s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf031f5b7e100 (FpiDeviceRealtek at 0x1ba6dce0)>, 6, None, None, None) 315s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf031f5b7e100 (FpiDeviceRealtek at 0x1ba6dce0)>, 7, None, None, None) 315s enroll progress: (<__gi__.FpiDeviceRealtek object at 0xf031f5b7e100 (FpiDeviceRealtek at 0x1ba6dce0)>, 8, None, None, None) 315s enroll done 315s listing 315s listing done 315s verifying 315s verify done 315s async identifying 315s indentification_done: 315s deleting 315s delete done 315s ** (umockdev-run:2508): DEBUG: 05:02:14.294: umockdev.vala:154: Removing test bed /tmp/umockdev.X14C22 315s (umockdev-run:2508): GLib-DEBUG: 05:02:14.299: unsetenv() is not thread-safe and should not be used after threads are created 315s PASS: libfprint-2/driver-realtek-5816.test 315s Running test: libfprint-2/driver-egis0570.test 315s ** (umockdev-run:2520): DEBUG: 05:02:14.360: umockdev.vala:127: Created udev test bed /tmp/umockdev.N2QG22 315s ** (umockdev-run:2520): DEBUG: 05:02:14.360: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 315s ** (umockdev-run:2520): DEBUG: 05:02:14.361: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 315s ** (umockdev-run:2520): DEBUG: 05:02:14.364: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.N2QG22/dev/bus/usb/001/005 315s ** (umockdev-run:2520): DEBUG: 05:02:14.364: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 315s ** (umockdev-run:2520): DEBUG: 05:02:14.365: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 315s ** (umockdev-run:2520): DEBUG: 05:02:14.367: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.N2QG22/dev/bus/usb/001/001 315s ** (umockdev-run:2520): DEBUG: 05:02:14.367: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 315s ** (umockdev-run:2520): DEBUG: 05:02:14.368: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 315s (process:2524): libfprint-context-DEBUG: 05:02:14.476: Initializing FpContext (libfprint version 1.94.9+tod1) 315s (process:2524): libfprint-tod-DEBUG: 05:02:14.476: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 315s (process:2524): libfprint-context-DEBUG: 05:02:14.478: No driver found for USB device 1D6B:0002 315s (process:2524): libfprint-device-DEBUG: 05:02:14.478: Device reported probe completion 315s (process:2524): libfprint-device-DEBUG: 05:02:14.478: Completing action FPI_DEVICE_ACTION_PROBE in idle! 315s (process:2524): libfprint-device-DEBUG: 05:02:14.479: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.480: Image device open completed 315s (process:2524): libfprint-device-DEBUG: 05:02:14.481: Device reported open completion 315s (process:2524): libfprint-device-DEBUG: 05:02:14.481: Completing action FPI_DEVICE_ACTION_OPEN in idle! 315s (process:2524): libfprint-device-DEBUG: 05:02:14.481: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 315s (process:2524): libfprint-device-DEBUG: 05:02:14.481: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.481: Activating image device 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.481: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.481: [egis0570] SM_STATES_NUM entering state 0 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.481: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.481: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.481: Image device activation completed 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.481: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.482: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 315s (process:2524): libfprint-device-DEBUG: 05:02:14.482: Device reported finger status change: FP_FINGER_STATUS_NEEDED 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.482: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.482: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.483: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.483: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.484: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.485: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.486: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.486: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.487: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.488: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.489: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.489: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.490: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.490: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.491: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.491: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.492: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.493: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.493: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.494: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.495: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.495: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.496: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.496: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.497: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.498: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.498: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.499: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.500: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.500: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.501: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.501: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.502: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.502: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.503: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.503: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.504: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.504: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.505: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.506: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.506: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.507: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.508: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.508: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.509: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.509: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.510: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.510: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.510: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.510: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.510: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.511: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.511: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.512: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.512: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.513: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.514: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.514: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.514: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.514: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.514: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.514: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.514: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.514: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.514: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.514: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.514: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.515: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.515: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.516: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.516: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.517: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.518: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.518: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.518: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.519: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.519: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.519: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.519: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.519: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.519: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.519: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.519: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.519: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.520: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.520: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.521: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.521: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.522: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.522: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.523: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.523: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.524: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.524: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.524: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.524: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.524: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.524: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.524: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.524: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.524: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.524: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.525: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.526: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.526: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.527: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.527: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.528: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.528: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.529: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.529: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.529: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.529: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.529: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.529: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.529: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.529: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.529: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.529: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.530: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.530: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.531: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.531: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.532: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.533: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.533: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.533: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.533: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.533: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.533: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.533: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.533: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.533: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.533: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.533: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.534: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.534: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.535: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.535: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.536: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.536: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.537: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.537: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.538: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.538: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.538: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.538: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.538: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.538: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.538: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.538: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.538: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.539: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.539: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.540: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.540: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.541: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.541: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.542: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.542: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.543: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.543: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.543: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.543: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.543: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.543: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.543: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.543: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.543: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.543: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.544: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.544: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.545: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.546: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.546: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.547: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.547: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.547: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.547: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.547: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.547: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.547: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.547: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.547: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.547: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.547: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.548: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.548: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.549: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.549: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.550: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.550: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.551: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.551: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.552: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.552: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.552: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.552: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.552: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.552: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.552: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.552: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.552: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.552: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.553: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.554: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.554: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.555: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.555: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.556: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.556: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.557: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.557: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.557: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.557: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.557: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.557: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.557: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.557: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.557: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.557: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.558: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.559: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.559: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.560: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.560: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.561: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.561: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.562: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.562: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.562: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.562: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.562: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.562: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.562: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.562: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.562: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.562: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.562: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.563: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.564: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.564: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.565: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.566: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.566: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.566: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.566: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.566: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.566: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.566: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.566: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.566: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.566: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.566: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.567: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.567: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.568: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.568: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.569: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.569: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.570: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.570: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.571: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.571: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.571: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.571: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.571: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.571: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.571: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.571: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.571: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.572: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.572: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.573: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.573: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.574: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.575: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.575: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.575: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.576: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.576: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.576: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.576: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.576: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.576: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.576: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.576: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.576: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.577: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.577: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.578: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.578: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.579: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.579: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.580: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.580: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-device-DEBUG: 05:02:14.581: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.581: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.581: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.581: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.582: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.582: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.582: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.582: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.582: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.582: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.582: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.583: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.584: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.584: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.585: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.586: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.587: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.587: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.588: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.588: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.588: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.588: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.588: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.588: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.588: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.588: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.588: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.589: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.589: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.590: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.591: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.591: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.592: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.592: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.593: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.593: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.593: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.593: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.593: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.593: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.593: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.593: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.593: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.593: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.594: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.594: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.595: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.595: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.596: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.596: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.597: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.597: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.598: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.598: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.598: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.598: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.598: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.598: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.598: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.598: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.598: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.599: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.599: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.600: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.600: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.601: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.601: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.602: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.602: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.603: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.603: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.603: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.603: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.603: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.603: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.603: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.603: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.603: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.604: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.604: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.605: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.605: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.606: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.606: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.607: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.607: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.608: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.608: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.608: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.608: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.608: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.608: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.608: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.608: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.608: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.608: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.609: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.609: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.610: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.611: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.611: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.612: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.612: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.613: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.613: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.613: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.613: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.613: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.613: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.613: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.613: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.613: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.614: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.614: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.615: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.615: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.616: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.617: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.617: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.617: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.618: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.618: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.618: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.618: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.618: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.618: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.618: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.618: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.618: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.619: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.619: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.620: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.620: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.621: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.622: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.623: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.623: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.623: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.623: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.623: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.623: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.623: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.623: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.623: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.623: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.623: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.624: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.624: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.625: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.626: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.626: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.627: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.628: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.628: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.628: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.628: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.628: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.628: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.628: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.628: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.628: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.628: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.628: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.629: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.629: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.630: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.630: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.631: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.632: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.633: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.633: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.633: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.633: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.633: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.633: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.633: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.633: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.633: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.633: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.633: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.634: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.634: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.635: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.636: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.636: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.637: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.638: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.638: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.638: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.638: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.638: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.638: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.638: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.638: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.638: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.638: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.638: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.639: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.639: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.640: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.641: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.642: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.642: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.643: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.643: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.644: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.644: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.644: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.644: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.644: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.644: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.644: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.644: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.644: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.644: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.645: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.645: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.646: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.647: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.647: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.648: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.648: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.649: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.649: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.649: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.649: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.649: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.649: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.649: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.649: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.649: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.649: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.650: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.651: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.651: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.652: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.653: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.654: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.654: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.655: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.655: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.655: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.655: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.655: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.655: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.655: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.655: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.655: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.655: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.656: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.656: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.657: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.658: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.658: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.659: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.659: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.660: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.660: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.660: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.660: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.660: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.660: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.660: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.660: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.660: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.660: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.661: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.661: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.662: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.663: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.663: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.664: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.664: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.665: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.665: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.665: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.665: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.665: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.665: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.665: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.665: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.665: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.665: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.666: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.666: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.667: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.668: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.668: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.669: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.669: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.670: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.670: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.670: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.670: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.670: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.670: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.670: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.670: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.670: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.670: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.671: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.672: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.672: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.673: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.673: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.674: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.674: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.675: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.675: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.675: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.675: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.675: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.675: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.675: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.675: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.675: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.675: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.676: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.677: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.677: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.678: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.678: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.679: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.679: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.680: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.680: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.680: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.680: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.680: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.680: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.680: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.680: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.680: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.680: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.681: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.682: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.682: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.683: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.683: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.684: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.684: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.685: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.685: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.685: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.685: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.685: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.685: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.685: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.685: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.685: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.685: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.686: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.686: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.687: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.688: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.688: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.689: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.689: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.690: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.690: Finger status (picture number, mean) : 1 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.690: Finger status (picture number, mean) : 2 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.690: Finger status (picture number, mean) : 3 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.690: Finger status (picture number, mean) : 4 , 0 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.690: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.690: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.690: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.690: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.690: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.691: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.692: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.692: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.693: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.693: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.694: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.694: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.695: Finger status (picture number, mean) : 0 , 0 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.695: Finger status (picture number, mean) : 1 , 1 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.695: Finger status (picture number, mean) : 2 , 2 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.695: Finger status (picture number, mean) : 3 , 3 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.695: Finger status (picture number, mean) : 4 , 6 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.695: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.695: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.695: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.695: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.695: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.696: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.697: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.697: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.698: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.698: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.699: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.699: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.700: Finger status (picture number, mean) : 0 , 11 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.700: Finger status (picture number, mean) : 1 , 16 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.700: Finger status (picture number, mean) : 2 , 23 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.700: Finger status (picture number, mean) : 3 , 28 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.700: Finger status (picture number, mean) : 4 , 32 315s (process:2524): libfprint-device-DEBUG: 05:02:14.700: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.700: Image device reported finger status: on 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.700: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 315s (process:2524): libfprint-device-DEBUG: 05:02:14.700: Device reported finger status change: FP_FINGER_STATUS_NEEDED 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.700: Image device reported finger status: off 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.700: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.700: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.700: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.701: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.701: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.702: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.702: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.703: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.704: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.704: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.704: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.705: Finger status (picture number, mean) : 0 , 38 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.705: Finger status (picture number, mean) : 1 , 43 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.705: Finger status (picture number, mean) : 2 , 48 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.705: Finger status (picture number, mean) : 3 , 54 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.705: Finger status (picture number, mean) : 4 , 58 315s (process:2524): libfprint-device-DEBUG: 05:02:14.705: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.705: Image device reported finger status: on 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.705: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.705: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.705: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.706: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.706: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.707: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.707: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.708: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.709: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.709: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.709: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.710: Finger status (picture number, mean) : 0 , 62 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.710: Finger status (picture number, mean) : 1 , 68 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.710: Finger status (picture number, mean) : 2 , 71 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.710: Finger status (picture number, mean) : 3 , 73 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.710: Finger status (picture number, mean) : 4 , 77 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.710: Image device reported finger status: on 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.710: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.710: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.710: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.711: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.711: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.712: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.712: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.713: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.714: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.714: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.714: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.715: Finger status (picture number, mean) : 0 , 79 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.715: Finger status (picture number, mean) : 1 , 79 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.715: Finger status (picture number, mean) : 2 , 82 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.715: Finger status (picture number, mean) : 3 , 84 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.715: Finger status (picture number, mean) : 4 , 85 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.715: Image device reported finger status: on 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.715: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.715: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.715: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.716: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.716: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.717: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.717: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.718: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.719: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.719: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.719: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.720: Finger status (picture number, mean) : 0 , 88 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.720: Finger status (picture number, mean) : 1 , 89 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.720: Finger status (picture number, mean) : 2 , 90 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.720: Finger status (picture number, mean) : 3 , 92 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.720: Finger status (picture number, mean) : 4 , 92 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.720: Image device reported finger status: on 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.720: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.720: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.720: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.721: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.721: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.722: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.723: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.723: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.724: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.725: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.725: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.726: Finger status (picture number, mean) : 0 , 93 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.726: Finger status (picture number, mean) : 1 , 94 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.726: Finger status (picture number, mean) : 2 , 95 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.726: Finger status (picture number, mean) : 3 , 96 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.726: Finger status (picture number, mean) : 4 , 97 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.726: Image device reported finger status: on 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.726: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.726: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.726: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.726: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.727: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.728: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.728: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.729: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.729: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.730: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.730: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.731: Finger status (picture number, mean) : 0 , 97 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.731: Finger status (picture number, mean) : 1 , 95 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.731: Finger status (picture number, mean) : 2 , 95 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.731: Finger status (picture number, mean) : 3 , 96 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.731: Finger status (picture number, mean) : 4 , 97 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.731: Image device reported finger status: on 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.731: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.731: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.731: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.732: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.732: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.733: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.734: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.734: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.735: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.736: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.736: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.736: Finger status (picture number, mean) : 0 , 96 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.736: Finger status (picture number, mean) : 1 , 97 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.736: Finger status (picture number, mean) : 2 , 98 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.736: Finger status (picture number, mean) : 3 , 98 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.736: Finger status (picture number, mean) : 4 , 98 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.736: Image device reported finger status: on 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.736: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.736: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.736: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.737: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.738: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.739: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.739: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.740: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.741: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.742: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.742: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.743: Finger status (picture number, mean) : 0 , 98 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.743: Finger status (picture number, mean) : 1 , 99 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.743: Finger status (picture number, mean) : 2 , 100 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.743: Finger status (picture number, mean) : 3 , 99 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.743: Finger status (picture number, mean) : 4 , 97 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.743: Image device reported finger status: on 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.743: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.743: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.743: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.743: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.744: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.745: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.745: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.746: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.747: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.748: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.748: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.748: Finger status (picture number, mean) : 0 , 98 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.748: Finger status (picture number, mean) : 1 , 98 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.748: Finger status (picture number, mean) : 2 , 98 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.748: Finger status (picture number, mean) : 3 , 95 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.748: Finger status (picture number, mean) : 4 , 91 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.748: Image device reported finger status: on 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.748: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.748: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.748: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.749: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.750: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.751: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.751: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.752: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.753: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.754: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.754: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.755: Finger status (picture number, mean) : 0 , 88 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.755: Finger status (picture number, mean) : 1 , 88 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.755: Finger status (picture number, mean) : 2 , 88 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.755: Finger status (picture number, mean) : 3 , 87 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.755: Finger status (picture number, mean) : 4 , 89 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.755: Image device reported finger status: on 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.755: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.755: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.755: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.755: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.756: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.757: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.757: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.758: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.759: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.760: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.760: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.761: Finger status (picture number, mean) : 0 , 88 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.761: Finger status (picture number, mean) : 1 , 89 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.761: Finger status (picture number, mean) : 2 , 90 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.761: Finger status (picture number, mean) : 3 , 91 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.761: Finger status (picture number, mean) : 4 , 89 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.761: Image device reported finger status: on 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.761: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.761: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.761: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.762: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.762: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.763: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.764: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.765: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.765: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.766: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.766: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.767: Finger status (picture number, mean) : 0 , 90 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.767: Finger status (picture number, mean) : 1 , 89 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.767: Finger status (picture number, mean) : 2 , 85 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.767: Finger status (picture number, mean) : 3 , 75 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.767: Finger status (picture number, mean) : 4 , 46 315s (process:2524): libfprint-image_device-DEBUG: 05:02:14.767: Image device reported finger status: on 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.767: [egis0570] SM_STATES_NUM entering state 5 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.767: [egis0570] SM_STATES_NUM entering state 1 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.767: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.767: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.768: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.769: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.769: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.770: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.771: [egis0570] SM_STATES_NUM entering state 2 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.772: [egis0570] SM_STATES_NUM entering state 3 315s (process:2524): libfprint-SSM-DEBUG: 05:02:14.772: [egis0570] SM_STATES_NUM entering state 4 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.773: Finger status (picture number, mean) : 0 , 17 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.773: Finger status (picture number, mean) : 1 , 14 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.773: Finger status (picture number, mean) : 2 , 15 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.773: Finger status (picture number, mean) : 3 , 15 315s (process:2524): libfprint-egis0570-DEBUG: 05:02:14.773: Finger status (picture number, mean) : 4 , 15 315s (process:2524): libfprint-assembling-DEBUG: 05:02:14.857: calc delta completed in 0.084312 secs 315s (process:2524): libfprint-assembling-DEBUG: 05:02:14.941: calc delta completed in 0.083890 secs 315s (process:2524): libfprint-assembling-DEBUG: 05:02:14.941: errors: 10243 rev: 29954 316s (process:2524): libfprint-assembling-DEBUG: 05:02:15.025: calc delta completed in 0.083839 secs 316s (process:2524): libfprint-assembling-DEBUG: 05:02:15.025: height is 292 316s (process:2524): libfprint-image_device-DEBUG: 05:02:15.027: Image device captured an image 316s (process:2524): libfprint-image_device-DEBUG: 05:02:15.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 316s (process:2524): libfprint-device-DEBUG: 05:02:15.027: Device reported finger status change: FP_FINGER_STATUS_PRESENT 316s (process:2524): libfprint-device-DEBUG: 05:02:15.027: Device reported finger status change: FP_FINGER_STATUS_NONE 316s (process:2524): libfprint-image_device-DEBUG: 05:02:15.027: Image device reported finger status: off 316s (process:2524): libfprint-image_device-DEBUG: 05:02:15.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 316s (process:2524): libfprint-image_device-DEBUG: 05:02:15.027: Deactivating image device 316s (process:2524): libfprint-image_device-DEBUG: 05:02:15.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 316s (process:2524): libfprint-SSM-DEBUG: 05:02:15.027: [egis0570] SM_STATES_NUM entering state 5 316s (process:2524): libfprint-SSM-DEBUG: 05:02:15.027: [egis0570] SM_STATES_NUM entering state 1 316s (process:2524): libfprint-egis0570-DEBUG: 05:02:15.027: deactivating, marking completed 316s (process:2524): libfprint-SSM-DEBUG: 05:02:15.027: [egis0570] SM_STATES_NUM completed successfully 316s (process:2524): libfprint-image_device-DEBUG: 05:02:15.027: Image device deactivation completed 316s (process:2524): libfprint-image_device-DEBUG: 05:02:15.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 316s (process:2524): libfprint-image-DEBUG: 05:02:15.079: Minutiae scan completed in 0.051436 secs 316s (process:2524): libfprint-device-DEBUG: 05:02:15.079: Device reported capture completion 316s (process:2524): libfprint-device-DEBUG: 05:02:15.079: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 316s (process:2524): libfprint-device-DEBUG: 05:02:15.079: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 316s (process:2524): libfprint-image_device-DEBUG: 05:02:15.080: Image device close completed 316s (process:2524): libfprint-device-DEBUG: 05:02:15.080: Device reported close completion 316s (process:2524): libfprint-device-DEBUG: 05:02:15.081: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 316s (process:2524): libfprint-device-DEBUG: 05:02:15.081: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 316s ** (umockdev-run:2520): DEBUG: 05:02:15.355: umockdev.vala:154: Removing test bed /tmp/umockdev.N2QG22 316s (umockdev-run:2520): GLib-DEBUG: 05:02:15.359: unsetenv() is not thread-safe and should not be used after threads are created 316s Comparing PNGs /tmp/libfprint-umockdev-test-zfl1s3gu/capture.png and /usr/share/installed-tests/libfprint-2/egis0570/capture.png 316s PASS: libfprint-2/driver-egis0570.test 316s Running test: libfprint-2/fp-context.test 316s TAP version 14 316s # random seed: R02Se819b98f015d9a0c0042808d54f44e35 316s 1..9 316s # Start of context tests 316s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 316s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 316s ok 1 /context/new 316s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 316s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 316s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 316s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 316s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 316s ok 2 /context/no-devices 316s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 316s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 316s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 316s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 316s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 316s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 316s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-8KJL22/virtual_image.socket 316s # libfprint-context-DEBUG: created 316s # libfprint-device-DEBUG: Device reported probe completion 316s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 316s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 316s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 316s ok 3 /context/has-virtual-device 316s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 316s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 316s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 316s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 316s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 316s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 316s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-Y7PL22/virtual_image.socket 316s # libfprint-context-DEBUG: created 316s # libfprint-device-DEBUG: Device reported probe completion 316s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 316s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 316s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 316s ok 4 /context/enumerates-new-devices 316s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 316s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 316s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 316s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 316s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 316s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 316s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-0WOL22/virtual_image.socket 316s # libfprint-context-DEBUG: created 316s # libfprint-device-DEBUG: Device reported probe completion 316s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 316s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 316s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 316s ok 5 /context/remove-device-closed 316s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 316s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 316s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 316s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 316s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 316s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 316s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-55NL22/virtual_image.socket 316s # libfprint-context-DEBUG: created 316s # libfprint-device-DEBUG: Device reported probe completion 316s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 316s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 316s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2531): libfprint-virtual_image-DEBUG: 05:02:15.460: 93378896: ../libfprint/drivers/virtual-image.c:216 316s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2531): libfprint-virtual_device_connection-DEBUG: 05:02:15.460: 93378987: ../libfprint/drivers/virtual-device-listener.c:153 316s # libfprint-image_device-DEBUG: Image device open completed 316s # libfprint-device-DEBUG: Device reported open completion 316s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 316s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 316s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2531): libfprint-virtual_image-DEBUG: 05:02:15.561: 93479489: ../libfprint/drivers/virtual-image.c:244 316s # libfprint-image_device-DEBUG: Image device close completed 316s # libfprint-device-DEBUG: Device reported close completion 316s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 316s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 316s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 316s ok 6 /context/remove-device-closing 316s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 316s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 316s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 316s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 316s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 316s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 316s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-VA9312/virtual_image.socket 316s # libfprint-context-DEBUG: created 316s # libfprint-device-DEBUG: Device reported probe completion 316s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 316s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 316s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2531): libfprint-virtual_image-DEBUG: 05:02:15.665: 93583533: ../libfprint/drivers/virtual-image.c:216 316s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2531): libfprint-virtual_device_connection-DEBUG: 05:02:15.665: 93583565: ../libfprint/drivers/virtual-device-listener.c:153 316s # libfprint-image_device-DEBUG: Image device open completed 316s # libfprint-device-DEBUG: Device reported open completion 316s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 316s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 316s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2531): libfprint-virtual_image-DEBUG: 05:02:15.765: 93683992: ../libfprint/drivers/virtual-image.c:244 316s # libfprint-image_device-DEBUG: Image device close completed 316s # libfprint-device-DEBUG: Device reported close completion 316s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 316s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 316s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 316s ok 7 /context/remove-device-open 316s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 316s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 316s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 316s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 316s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 316s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 316s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-THU512/virtual_image.socket 316s # libfprint-context-DEBUG: created 316s # libfprint-device-DEBUG: Device reported probe completion 316s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 316s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 316s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2531): libfprint-virtual_image-DEBUG: 05:02:15.869: 93787662: ../libfprint/drivers/virtual-image.c:216 316s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2531): libfprint-virtual_device_connection-DEBUG: 05:02:15.869: 93787695: ../libfprint/drivers/virtual-device-listener.c:153 317s # libfprint-image_device-DEBUG: Image device open completed 317s # libfprint-device-DEBUG: Device reported open completion 317s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 317s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 317s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2531): libfprint-virtual_image-DEBUG: 05:02:15.970: 93888201: ../libfprint/drivers/virtual-image.c:244 317s # libfprint-image_device-DEBUG: Image device close completed 317s # libfprint-device-DEBUG: Device reported close completion 317s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 317s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 317s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 317s ok 8 /context/remove-device-opening 317s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created 317s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 317s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1?: No such file or directory 317s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 317s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 317s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 317s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-2QCB22/virtual_image.socket 317s # libfprint-context-DEBUG: created 317s # libfprint-device-DEBUG: Device reported probe completion 317s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 317s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 317s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2531): libfprint-virtual_image-DEBUG: 05:02:16.073: 93991902: ../libfprint/drivers/virtual-image.c:216 317s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2531): libfprint-virtual_device_connection-DEBUG: 05:02:16.073: 93991930: ../libfprint/drivers/virtual-device-listener.c:153 317s # libfprint-image_device-DEBUG: Image device open completed 317s # libfprint-device-DEBUG: Device reported open completion 317s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 317s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 317s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 317s # libfprint-image_device-DEBUG: Activating image device 317s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 317s # libfprint-image_device-DEBUG: Image device activation completed 317s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 317s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 317s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED 317s # libfprint-image_device-DEBUG: Deactivating image device 317s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 317s # libfprint-image_device-DEBUG: Image device deactivation completed 317s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 317s # libfprint-device-DEBUG: Device reported generic error (The driver encountered a protocol error with the device.) during action; action was: FPI_DEVICE_ACTION_ENROLL 317s # libfprint-device-DEBUG: Device reported enroll completion 317s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE 317s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 317s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 317s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2531): libfprint-virtual_image-DEBUG: 05:02:16.174: 94092629: ../libfprint/drivers/virtual-image.c:244 317s # libfprint-image_device-DEBUG: Image device close completed 317s # libfprint-device-DEBUG: Device reported close completion 317s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 317s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 317s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created 317s ok 9 /context/remove-device-active 317s # End of context tests 317s PASS: libfprint-2/fp-context.test 317s Running test: libfprint-2/driver-upektc_img.test 317s ** (umockdev-run:2555): DEBUG: 05:02:16.327: umockdev.vala:127: Created udev test bed /tmp/umockdev.AXUI22 317s ** (umockdev-run:2555): DEBUG: 05:02:16.327: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 317s ** (umockdev-run:2555): DEBUG: 05:02:16.329: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 (subsystem usb) 317s ** (umockdev-run:2555): DEBUG: 05:02:16.331: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.AXUI22/dev/bus/usb/001/003 317s ** (umockdev-run:2555): DEBUG: 05:02:16.332: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1 317s ** (umockdev-run:2555): DEBUG: 05:02:16.333: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1 (subsystem usb) 317s ** (umockdev-run:2555): DEBUG: 05:02:16.334: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.AXUI22/dev/bus/usb/001/002 317s ** (umockdev-run:2555): DEBUG: 05:02:16.335: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1 317s ** (umockdev-run:2555): DEBUG: 05:02:16.335: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1 (subsystem usb) 317s ** (umockdev-run:2555): DEBUG: 05:02:16.338: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.AXUI22/dev/bus/usb/001/001 317s ** (umockdev-run:2555): DEBUG: 05:02:16.338: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0 317s ** (umockdev-run:2555): DEBUG: 05:02:16.338: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0 (subsystem pci) 317s (process:2559): libfprint-context-DEBUG: 05:02:16.445: Initializing FpContext (libfprint version 1.94.9+tod1) 317s (process:2559): libfprint-tod-DEBUG: 05:02:16.445: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 317s (process:2559): libfprint-context-DEBUG: 05:02:16.448: No driver found for USB device 8087:0020 317s (process:2559): libfprint-context-DEBUG: 05:02:16.448: No driver found for USB device 1D6B:0002 317s (process:2559): libfprint-device-DEBUG: 05:02:16.448: Device reported probe completion 317s (process:2559): libfprint-device-DEBUG: 05:02:16.448: Completing action FPI_DEVICE_ACTION_PROBE in idle! 317s (process:2559): libfprint-device-DEBUG: 05:02:16.448: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.450: Image device open completed 317s (process:2559): libfprint-device-DEBUG: 05:02:16.450: Device reported open completion 317s (process:2559): libfprint-device-DEBUG: 05:02:16.450: Completing action FPI_DEVICE_ACTION_OPEN in idle! 317s (process:2559): libfprint-device-DEBUG: 05:02:16.450: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 317s (process:2559): libfprint-device-DEBUG: 05:02:16.450: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.450: Activating image device 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.450: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.450: [upektc_img] ACTIVATE_NUM_STATES entering state 0 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.451: [upektc_img] ACTIVATE_NUM_STATES entering state 1 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.452: [upektc_img] ACTIVATE_NUM_STATES entering state 2 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.453: [upektc_img] ACTIVATE_NUM_STATES entering state 3 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.454: [upektc_img] ACTIVATE_NUM_STATES entering state 4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.454: [upektc_img] ACTIVATE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.455: [upektc_img] ACTIVATE_NUM_STATES entering state 6 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.456: [upektc_img] ACTIVATE_NUM_STATES entering state 7 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.456: [upektc_img] ACTIVATE_NUM_STATES entering state 8 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.457: [upektc_img] ACTIVATE_NUM_STATES entering state 9 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.458: [upektc_img] ACTIVATE_NUM_STATES entering state 10 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.458: [upektc_img] ACTIVATE_NUM_STATES entering state 11 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.459: Sensor type : TCS4x, width x height: 192 x 512 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.459: [upektc_img] ACTIVATE_NUM_STATES completed successfully 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.459: Image device activation completed 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.459: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.459: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 317s (process:2559): libfprint-device-DEBUG: 05:02:16.459: Device reported finger status change: FP_FINGER_STATUS_NEEDED 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.459: [upektc_img] CAPTURE_NUM_STATES entering state 0 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.460: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.461: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.461: 18th byte is 0c 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.461: [upektc_img] CAPTURE_NUM_STATES entering state 3 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.461: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.462: request completed, len: 0040 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.462: [upektc_img] CAPTURE_NUM_STATES entering state 4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.463: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.464: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.464: 18th byte is 00 317s (process:2559): libfprint-device-DEBUG: 05:02:16.464: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.464: [upektc_img] CAPTURE_NUM_STATES entering state 3 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.465: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.465: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.465: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.465: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.465: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.466: request completed, len: 07c4 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.466: Image device reported finger status: on 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.466: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.466: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.467: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.467: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.467: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.467: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.467: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.468: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.468: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.469: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.469: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.469: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.469: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.469: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.470: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.470: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.471: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.471: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.471: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.471: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.471: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.472: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.472: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.472: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.473: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.473: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.473: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.473: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.474: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.474: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.474: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.475: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.475: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.475: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.475: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.476: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.476: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.476: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.477: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.477: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.477: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.477: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.478: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.478: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.478: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.479: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.479: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.479: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.479: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.479: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.479: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.480: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.481: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.481: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.481: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.481: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.481: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.481: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.482: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.482: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.482: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.482: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.482: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.483: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.483: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.484: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.484: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.484: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.484: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.484: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.485: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.485: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.485: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.486: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.486: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.486: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.486: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.487: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.487: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.487: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.488: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.488: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.488: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.488: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.489: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.489: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.490: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.490: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.490: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.490: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.490: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.491: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.491: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.492: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.493: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.493: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.493: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.493: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.493: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.493: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.494: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.495: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.495: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.495: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.495: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.496: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.496: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.496: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.497: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.497: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.497: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.497: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.498: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.498: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.499: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.500: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.500: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.500: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.500: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.500: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.500: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.501: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.502: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.502: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.502: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.502: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.503: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.503: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.503: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.504: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.504: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.504: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.504: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.505: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.505: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.505: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.506: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.506: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.506: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.506: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.507: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.507: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.508: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.508: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.508: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.508: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.508: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.509: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.509: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.510: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.510: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.510: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.510: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.510: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.511: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.511: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.512: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.512: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.512: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.512: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.512: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.513: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.513: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.514: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.514: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.514: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.514: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.514: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.515: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.515: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.516: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.517: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.517: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.517: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.517: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.518: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.518: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.518: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.519: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.519: response_size is 2052, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.519: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.519: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.520: request completed, len: 07c4 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.520: [upektc_img] CAPTURE_NUM_STATES entering state 5 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.520: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.521: request completed, len: 0040 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.521: response_size is 186, actual_length is 64 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.521: Waiting for rest of transfer 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.521: [upektc_img] CAPTURE_NUM_STATES entering state 1 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.521: request completed, len: 007a 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.521: Image size is 55296 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.521: Image device captured an image 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.522: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 317s (process:2559): libfprint-device-DEBUG: 05:02:16.522: Device reported finger status change: FP_FINGER_STATUS_PRESENT 317s (process:2559): libfprint-device-DEBUG: 05:02:16.522: Device reported finger status change: FP_FINGER_STATUS_NONE 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.522: Image device reported finger status: off 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.522: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.522: Deactivating image device 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.522: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.522: [upektc_img] CAPTURE_NUM_STATES completed successfully 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.522: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.523: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 317s (process:2559): libfprint-SSM-DEBUG: 05:02:16.524: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 317s (process:2559): libfprint-upektc_img-DEBUG: 05:02:16.524: Deactivate completed 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.524: Image device deactivation completed 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.524: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 317s (process:2559): libfprint-image-DEBUG: 05:02:16.533: Minutiae scan completed in 0.011594 secs 317s (process:2559): libfprint-device-DEBUG: 05:02:16.534: Device reported capture completion 317s (process:2559): libfprint-device-DEBUG: 05:02:16.534: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 317s (process:2559): libfprint-device-DEBUG: 05:02:16.534: Updated temperature model after 0.08 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 317s (process:2559): libfprint-image_device-DEBUG: 05:02:16.534: Image device close completed 317s (process:2559): libfprint-device-DEBUG: 05:02:16.534: Device reported close completion 317s (process:2559): libfprint-device-DEBUG: 05:02:16.534: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 317s (process:2559): libfprint-device-DEBUG: 05:02:16.534: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 317s ** (umockdev-run:2555): DEBUG: 05:02:16.639: umockdev.vala:154: Removing test bed /tmp/umockdev.AXUI22 317s (umockdev-run:2555): GLib-DEBUG: 05:02:16.644: unsetenv() is not thread-safe and should not be used after threads are created 317s Comparing PNGs /tmp/libfprint-umockdev-test-xln0cbcw/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img/capture.png 317s PASS: libfprint-2/driver-upektc_img.test 317s Running test: libfprint-2/driver-vfs7552.test 317s ** (umockdev-run:2568): DEBUG: 05:02:16.726: umockdev.vala:127: Created udev test bed /tmp/umockdev.Z3V212 317s ** (umockdev-run:2568): DEBUG: 05:02:16.726: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 317s ** (umockdev-run:2568): DEBUG: 05:02:16.727: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 317s ** (umockdev-run:2568): DEBUG: 05:02:16.730: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Z3V212/dev/bus/usb/001/003 317s ** (umockdev-run:2568): DEBUG: 05:02:16.730: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 317s ** (umockdev-run:2568): DEBUG: 05:02:16.731: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 317s ** (umockdev-run:2568): DEBUG: 05:02:16.734: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.Z3V212/dev/bus/usb/001/001 317s ** (umockdev-run:2568): DEBUG: 05:02:16.734: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 317s ** (umockdev-run:2568): DEBUG: 05:02:16.734: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 317s (umockdev-run:2568): GLib-GIO-DEBUG: 05:02:16.736: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 317s (process:2572): libfprint-context-DEBUG: 05:02:16.857: Initializing FpContext (libfprint version 1.94.9+tod1) 317s (process:2572): libfprint-tod-DEBUG: 05:02:16.857: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 317s (process:2572): libfprint-context-DEBUG: 05:02:16.860: No driver found for USB device 1D6B:0002 317s (process:2572): libfprint-device-DEBUG: 05:02:16.860: Device reported probe completion 317s (process:2572): libfprint-device-DEBUG: 05:02:16.860: Completing action FPI_DEVICE_ACTION_PROBE in idle! 317s (process:2572): libfprint-device-DEBUG: 05:02:16.860: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.862: [vfs7552] DEV_OPEN_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.862: [vfs7552] DEVICE OPEN entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.862: Sending vfs7552_cmd_01 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.863: [vfs7552] DEVICE OPEN entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.863: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.864: Got 38 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.864: [vfs7552] DEVICE OPEN entering state 2 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.864: Sending vfs7552_cmd_19 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.865: [vfs7552] DEVICE OPEN entering state 3 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.865: Receiving 128 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.865: Got 68 bytes out of 128 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.865: [vfs7552] DEVICE OPEN entering state 4 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.865: Sending vfs7552_init_00 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.866: [vfs7552] DEVICE OPEN entering state 5 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.866: Receiving 64 bytes 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.867: [vfs7552] DEVICE OPEN entering state 6 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.867: Sending vfs7552_init_01 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.867: [vfs7552] DEVICE OPEN entering state 7 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.867: Receiving 64 bytes 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.868: [vfs7552] DEVICE OPEN entering state 8 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.868: Sending vfs7552_init_02 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.869: [vfs7552] DEVICE OPEN entering state 9 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.869: Receiving 64 bytes 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.870: [vfs7552] DEVICE OPEN entering state 10 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.870: Sending vfs7552_init_03 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.870: [vfs7552] DEVICE OPEN entering state 11 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.870: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.871: Got 10 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.871: [vfs7552] DEVICE OPEN entering state 12 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.871: Sending vfs7552_init_04 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.871: [vfs7552] DEVICE OPEN entering state 13 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.872: Receiving 64 bytes 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.872: [vfs7552] DEVICE OPEN completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.872: [vfs7552] DEV_OPEN_NUM_STATES completed successfully 317s (process:2572): libfprint-image_device-DEBUG: 05:02:16.872: Image device open completed 317s (process:2572): libfprint-device-DEBUG: 05:02:16.872: Device reported open completion 317s (process:2572): libfprint-device-DEBUG: 05:02:16.872: Completing action FPI_DEVICE_ACTION_OPEN in idle! 317s (process:2572): libfprint-device-DEBUG: 05:02:16.872: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 317s (process:2572): libfprint-device-DEBUG: 05:02:16.872: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 317s (process:2572): libfprint-image_device-DEBUG: 05:02:16.872: Activating image device 317s (process:2572): libfprint-image_device-DEBUG: 05:02:16.872: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 317s (process:2572): libfprint-image_device-DEBUG: 05:02:16.872: Image device activation completed 317s (process:2572): libfprint-image_device-DEBUG: 05:02:16.872: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 317s (process:2572): libfprint-image_device-DEBUG: 05:02:16.872: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 317s (process:2572): libfprint-device-DEBUG: 05:02:16.872: Device reported finger status change: FP_FINGER_STATUS_NEEDED 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.922: changing to 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.922: [vfs7552] ACTIVATE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.922: [vfs7552] ACTIVATE INIT entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.922: Sending vfs7552_image_start 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.923: [vfs7552] ACTIVATE INIT entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.923: Receiving 2048 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.924: Got 1962 bytes out of 2048 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.924: [vfs7552] ACTIVATE INIT completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.924: [vfs7552] ACTIVATE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.924: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.924: Receiving 8 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.925: Got 5 bytes out of 8 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.925: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.925: [vfs7552] ACTIVATE_NUM_STATES entering state 2 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.925: [vfs7552] ACTIVATE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.925: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.925: Receiving 8 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.925: Got 5 bytes out of 8 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.926: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.926: [vfs7552] ACTIVATE_NUM_STATES entering state 2 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.926: [vfs7552] ACTIVATE_NUM_STATES entering state 3 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.926: [vfs7552] ACTIVATE_NUM_STATES completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.926: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.926: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.926: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.926: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.927: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.927: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.927: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.927: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.927: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.927: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.928: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.928: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.928: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.928: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.929: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.929: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.929: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.929: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.929: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.929: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.930: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.930: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.931: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.931: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.931: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.931: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.931: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.931: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.932: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.932: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.932: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.932: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.932: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.932: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.933: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.933: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.934: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.934: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.934: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.934: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.934: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.934: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.935: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.935: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.935: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.935: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.935: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.936: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.936: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.936: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.936: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.936: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.937: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.937: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.937: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.937: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.937: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.937: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.938: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.938: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.939: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.939: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.939: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.939: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.939: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.940: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.940: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.940: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.940: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.940: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.941: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.941: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.941: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.941: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.941: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.941: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.942: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.942: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.942: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.942: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.942: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.942: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.943: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.943: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.943: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.944: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.944: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.944: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.944: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.944: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.945: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.945: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.945: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.945: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.946: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.946: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.946: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.946: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.946: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.946: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.947: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.947: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.948: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.948: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.948: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.948: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.948: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.948: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.949: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.949: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.949: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.949: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.949: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.949: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.950: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.950: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.950: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.950: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.951: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.951: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.951: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.951: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.951: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.951: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.952: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.952: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.952: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.952: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.952: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.952: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.953: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.953: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.954: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.954: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.954: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.954: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.954: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.954: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.955: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.955: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.955: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.955: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.955: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.955: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.956: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.956: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.956: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.956: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.957: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.957: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.957: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.957: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.957: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.957: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.958: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.958: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.958: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.958: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.958: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.958: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.959: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.959: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.960: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.960: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.960: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.960: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.960: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.960: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.961: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.961: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.961: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.961: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.961: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.961: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.962: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.962: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.962: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.962: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.963: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.963: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.964: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.964: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.964: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.964: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.964: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.964: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.965: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.965: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.965: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.965: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.965: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.965: Sending vfs7552_is_image_ready 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.965: [vfs7552] QUERY DATA READY entering state 1 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.965: Receiving 64 bytes 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.966: Got 6 bytes out of 64 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.966: [vfs7552] QUERY DATA READY completed successfully 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 317s (process:2572): libfprint-SSM-DEBUG: 05:02:16.966: [vfs7552] QUERY DATA READY entering state 0 317s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.966: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.967: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.967: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.967: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.967: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.967: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.967: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.968: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.968: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.968: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.968: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.968: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.968: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.969: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.969: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.970: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.970: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.970: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.970: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.970: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.970: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.971: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.971: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.971: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.971: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.972: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.972: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.972: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.972: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.972: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.972: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.973: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.973: Receiving 64 bytes 318s (process:2572): libfprint-device-DEBUG: 05:02:16.973: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.973: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.973: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.973: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.973: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.974: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.974: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.974: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.974: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.975: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.975: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.975: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.975: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.976: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.976: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.976: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.976: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.976: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.976: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.977: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.977: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.977: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.977: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.978: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.978: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.978: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.978: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.978: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.978: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.979: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.979: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.979: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.979: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.979: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.979: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.980: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.980: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.980: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.981: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.981: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.981: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.981: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.981: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.982: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.982: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.982: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.982: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.982: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.982: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.983: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.983: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.983: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.983: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.983: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.983: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.984: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.984: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.984: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.984: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.985: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.985: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.985: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.985: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.985: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.985: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.986: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.986: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.986: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.986: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.987: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.987: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.987: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.987: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.987: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.988: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.988: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.988: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.988: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.988: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.989: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.989: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.989: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.989: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.989: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.989: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.990: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.990: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.990: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.990: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.991: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.991: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.991: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.991: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.991: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.991: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.992: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.992: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.993: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.993: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.993: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.993: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.993: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.993: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.994: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.994: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.994: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.994: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.995: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.995: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.995: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.995: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.995: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.995: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.996: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.996: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.996: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.996: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.996: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.996: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.997: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.997: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.998: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.998: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.998: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.998: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.998: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.998: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.999: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.999: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:16.999: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:16.999: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.000: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.000: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.000: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.000: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.000: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.000: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.001: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.001: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.001: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.002: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.002: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.002: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.003: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.003: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.003: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.003: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.003: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.003: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.004: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.004: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.005: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.005: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.005: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.005: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.005: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.006: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.006: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.006: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.006: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.006: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.007: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.007: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.007: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.008: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.008: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.008: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.008: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.008: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.009: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.009: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.009: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.009: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.010: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.010: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.010: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.011: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.011: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.011: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.011: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.011: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.012: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.012: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.012: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.012: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.013: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.013: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.013: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.013: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.013: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.013: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.014: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.014: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.014: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.015: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.015: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.015: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.015: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.015: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.016: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.016: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.016: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.016: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.016: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.016: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.017: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.017: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.017: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.017: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.018: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.018: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.019: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.019: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.019: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.019: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.019: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.019: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.020: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.020: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.020: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.020: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.021: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.021: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.021: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.021: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.021: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.021: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.022: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.022: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.023: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.023: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.023: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.023: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.023: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.023: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.024: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.024: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.024: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.024: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.025: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.025: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.025: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.025: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.025: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.025: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.026: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.026: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.027: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.027: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.027: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.027: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.027: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.027: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.028: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.028: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.028: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.028: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.029: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.029: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.029: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.029: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.030: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.030: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.030: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.030: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.031: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.031: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.031: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.031: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.032: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.032: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.032: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.032: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.032: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.032: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.033: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.033: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.034: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.034: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.034: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.034: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.034: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.034: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.035: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.035: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.035: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.035: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.035: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.035: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.036: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.036: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.036: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.036: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.036: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.036: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.037: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.037: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.038: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.038: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.038: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.038: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.038: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.038: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.039: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.039: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.039: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.039: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.040: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.040: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.041: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.041: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.041: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.041: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.041: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.041: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.041: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.042: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.042: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.042: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.042: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.043: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.043: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.043: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.043: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.043: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.043: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.043: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.044: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.044: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.045: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.045: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.045: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.045: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.045: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.046: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.046: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.046: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.047: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.047: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.048: [vfs7552] CAPTURE_NUM_STATES entering state 4 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.048: variance_before = 396 318s 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.048: background stored 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.048: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.048: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.048: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.048: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.049: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.049: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.049: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.049: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.050: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.050: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.050: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.050: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.050: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.050: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.051: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.051: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.052: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.052: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.052: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.052: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.052: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.052: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.053: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.053: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.053: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.053: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.054: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.054: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.055: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.055: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.055: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.055: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.055: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.055: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.055: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.055: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.056: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.056: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.056: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.056: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.057: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.057: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.057: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.057: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.057: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.057: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.058: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.058: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.059: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.059: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.059: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.059: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.059: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.059: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.060: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.060: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.060: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.060: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.061: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.061: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.062: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.062: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.062: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.062: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.062: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.062: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.063: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.063: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.063: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.063: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.064: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.064: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.065: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.065: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.065: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.065: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.066: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.066: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.066: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.066: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.066: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.066: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.067: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.067: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.068: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.068: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.068: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.068: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.069: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.069: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.069: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.069: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.069: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.069: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.070: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.070: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.071: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.071: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.071: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.071: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.072: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.072: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.072: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.073: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.073: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.073: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.073: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.073: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.074: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.074: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.074: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.074: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.075: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.075: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.076: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.076: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.076: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.076: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.077: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.077: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.077: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.077: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.077: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.077: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.078: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.078: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.079: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.079: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.079: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.079: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.079: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.079: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.080: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.080: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.080: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.080: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.081: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.081: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.082: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.082: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.082: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.082: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.082: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.082: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.083: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.083: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.083: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.083: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.084: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.084: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.084: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.084: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.084: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.084: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.085: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.085: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.086: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.086: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.086: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.086: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.086: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.086: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.087: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.087: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.087: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.087: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.087: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.087: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.088: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.088: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.088: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.088: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.089: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.089: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.089: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.089: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.089: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.089: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.090: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.090: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.090: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.091: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.091: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.091: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.091: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.091: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.092: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.092: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.092: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.092: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.092: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.092: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.093: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.093: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.093: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.093: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.094: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.094: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.094: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.094: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.094: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.094: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.095: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.095: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.095: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.095: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.095: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.095: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.096: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.096: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.097: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.097: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.097: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.097: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.097: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.097: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.098: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.098: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.098: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.098: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.098: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.098: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.099: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.099: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.099: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.099: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.100: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.100: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.100: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.100: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.100: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.100: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.101: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.101: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.101: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.101: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.101: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.101: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.102: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.102: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.103: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.103: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.103: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.103: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.103: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.103: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.104: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.104: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.104: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.104: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.105: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.105: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.105: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.105: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.105: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.105: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.106: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.106: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.106: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.106: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.107: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.107: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.107: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.107: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.107: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.107: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.108: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.108: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.108: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.108: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.108: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.108: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.109: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.109: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.109: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.109: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.110: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.110: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.110: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.110: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.110: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.111: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.111: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.111: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.112: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.112: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.112: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.112: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.112: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.112: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.113: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.113: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.113: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.113: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.113: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.113: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.113: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.113: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.114: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.114: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.114: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.114: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.115: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.115: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.115: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.115: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.115: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.115: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.116: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.116: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.116: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.116: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.116: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.117: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.117: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.117: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.118: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.118: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.118: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.118: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.118: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.118: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.119: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.119: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.119: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.119: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.119: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.120: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.120: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.120: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.120: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.120: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.121: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.121: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.121: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.121: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.121: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.121: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.122: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.122: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.123: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.123: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.123: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.123: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.123: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.123: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.124: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.124: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.124: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.124: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.125: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.125: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.125: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.125: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.125: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.125: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.126: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.126: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.126: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.126: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.126: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.126: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.127: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.127: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.128: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.128: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.128: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.128: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.128: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.128: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.129: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.129: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.129: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.129: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.129: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.129: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.130: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.130: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.130: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.130: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.131: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.131: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.131: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.131: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.131: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.131: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.132: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.132: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.133: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.133: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.133: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.133: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.133: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.133: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.134: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.134: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.134: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.134: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.134: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.134: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.135: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.135: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.135: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.135: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.135: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.135: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.136: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.136: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.136: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.136: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.137: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.137: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.137: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.137: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.137: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.137: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.138: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.138: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.139: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.139: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.139: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.139: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.139: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.139: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.140: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.140: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.140: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.140: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.141: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.141: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.141: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.141: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.141: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.141: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.142: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.142: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.143: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.143: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.143: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.143: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.143: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.143: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.144: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.144: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.144: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.144: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.144: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.144: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.145: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.145: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.145: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.145: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.146: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.146: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.146: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.146: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.146: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.146: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.147: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.147: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.148: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.148: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.148: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.148: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.148: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.148: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.149: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.149: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.149: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.149: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.149: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.149: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.150: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.150: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.150: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.150: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.150: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.150: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.151: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.151: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.151: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.151: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.151: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.151: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.152: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.152: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.153: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.153: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.153: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.153: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.153: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.153: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.154: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.154: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.154: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.154: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.155: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.155: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.155: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.155: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.155: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.155: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.156: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.156: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.156: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.156: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.156: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.156: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.157: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.157: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.158: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.158: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.158: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.158: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.158: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.158: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.159: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.159: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.159: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.159: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.160: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.160: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.160: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.160: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.160: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.160: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.161: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.161: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.162: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.162: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.162: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.162: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.162: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.162: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.163: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.163: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.163: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.163: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.164: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.164: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.164: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.164: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.164: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.164: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.165: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.165: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.166: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.166: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.166: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.166: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.166: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.166: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.167: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.167: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.167: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.167: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.168: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.168: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.168: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.168: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.168: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.168: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.169: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.169: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.169: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.169: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.169: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.169: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.169: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.170: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.170: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.171: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.171: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.171: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.171: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.171: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.171: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.172: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.172: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.172: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.172: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.172: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.172: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.173: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.173: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.173: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.173: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.174: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.174: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.174: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.174: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.174: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.174: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.175: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.175: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.176: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.176: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.176: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.176: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.176: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.176: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.177: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.177: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.177: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.177: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.178: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.178: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.178: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.178: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.178: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.178: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.179: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.179: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.180: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.180: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.180: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.180: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.180: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.180: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.181: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.181: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.181: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.181: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.181: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.181: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.182: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.182: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.182: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.182: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.182: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.182: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.183: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.183: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.183: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.183: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.183: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.183: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.183: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.184: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.184: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.185: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.185: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.185: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.185: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.185: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.186: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.186: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.186: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.186: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.187: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.187: [vfs7552] CAPTURE_NUM_STATES entering state 4 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.187: Cleaning image 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.187: variance_after = 20 318s 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.187: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.187: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.188: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.188: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.188: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.188: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.188: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.188: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.189: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.189: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.190: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.190: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.190: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.190: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.190: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.190: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.191: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.191: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.191: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.191: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.191: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.191: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.192: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.192: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.192: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.192: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.193: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.193: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.193: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.193: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.193: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.193: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.194: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.194: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.194: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.195: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.195: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.195: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.195: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.195: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.196: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.196: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.196: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.196: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.196: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.196: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.197: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.197: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.197: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.197: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.197: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.197: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.198: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.198: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.198: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.198: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.199: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.199: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.199: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.199: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.199: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.199: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.200: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.200: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.200: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.201: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.201: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.201: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.201: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.201: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.201: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.202: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.202: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.202: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.202: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.202: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.203: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.203: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.203: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.203: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.203: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.204: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.204: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.204: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.204: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.204: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.204: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.205: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.205: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.205: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.206: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.206: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.206: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.206: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.206: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.207: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.207: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.207: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.207: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.207: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.207: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.208: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.208: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.208: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.208: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.209: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.209: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.209: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.209: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.209: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.209: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.210: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.210: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.210: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.210: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.210: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.210: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.211: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.211: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.212: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.212: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.212: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.212: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.212: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.212: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.213: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.213: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.213: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.213: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.213: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.213: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.214: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.214: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.214: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.214: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.214: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.215: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.215: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.215: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.215: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.215: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.216: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.216: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.216: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.216: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.216: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.216: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.217: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.217: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.217: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.217: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.218: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.218: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.218: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.218: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.219: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.219: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.219: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.219: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.220: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.220: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.220: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.220: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.220: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.220: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.221: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.221: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.222: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.222: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.222: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.222: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.222: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.222: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.223: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.223: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.223: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.223: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.223: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.223: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.224: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.224: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.224: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.224: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.224: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.224: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.225: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.225: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.225: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.225: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.225: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.225: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.226: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.226: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.227: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.227: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.227: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.227: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.227: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.227: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.228: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.228: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.228: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.228: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.228: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.228: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.229: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.229: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.229: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.229: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.230: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.230: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.230: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.230: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.230: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.230: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.231: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.231: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.231: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.231: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.231: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.231: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.232: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.232: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.233: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.233: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.233: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.233: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.233: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.233: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.234: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.234: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.234: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.234: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.234: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.234: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.235: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.235: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.235: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.235: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.236: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.236: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.236: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.236: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.236: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.236: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.237: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.237: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.238: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.238: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.238: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.238: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.238: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.238: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.239: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.239: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.239: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.239: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.239: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.239: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.240: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.240: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.240: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.240: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.241: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.241: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.241: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.241: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.241: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.241: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.242: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.242: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.243: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.243: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.243: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.243: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.243: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.243: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.244: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.244: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.244: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.244: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.245: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.245: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.245: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.245: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.245: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.245: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.246: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.246: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.246: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.247: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.247: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.247: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.247: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.247: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.248: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.248: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.248: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.248: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.248: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.248: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.249: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.249: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.249: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.249: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.250: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.250: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.250: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.250: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.250: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.250: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.251: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.251: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.251: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.251: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.251: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.251: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.252: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.252: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.253: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.253: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.253: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.253: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.253: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.253: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.254: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.254: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.254: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.254: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.254: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.254: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.255: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.255: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.255: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.255: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.256: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.256: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.256: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.256: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.256: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.256: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.257: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.257: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.258: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.258: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.258: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.258: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.259: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.259: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.259: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.259: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.259: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.259: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.260: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.260: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.261: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.261: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.261: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.261: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.262: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.262: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.262: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.262: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.262: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.262: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.263: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.263: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.264: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.264: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.264: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.264: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.264: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.264: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.265: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.265: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.265: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.265: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.265: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.266: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.266: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.266: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.266: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.266: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.267: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.267: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.268: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.268: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.268: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.268: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.268: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.269: [vfs7552] CAPTURE_NUM_STATES entering state 4 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.269: Cleaning image 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.269: variance_after = 18 318s 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.269: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.269: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.270: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.270: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.270: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.271: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.271: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.271: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.271: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.271: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.272: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.272: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.272: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.272: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.272: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.272: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.273: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.273: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.273: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.273: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.274: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.274: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.274: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.274: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.274: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.274: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.275: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.275: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.276: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.276: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.276: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.276: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.276: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.276: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.276: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.276: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.277: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.277: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.277: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.277: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.278: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.278: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.278: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.278: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.278: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.278: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.279: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.279: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.279: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.280: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.280: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.280: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.280: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.280: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.281: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.281: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.281: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.281: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.281: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.281: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.282: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.282: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.282: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.282: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.283: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.283: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.283: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.283: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.283: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.283: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.284: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.284: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.284: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.284: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.284: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.284: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.285: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.285: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.286: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.286: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.286: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.286: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.286: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.286: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.287: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.287: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.287: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.287: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.288: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.288: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.288: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.288: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.288: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.288: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.289: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.289: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.289: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.289: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.289: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.289: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.290: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.290: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.291: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.291: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.291: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.291: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.292: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.292: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.292: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.292: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.292: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.292: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.293: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.293: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.293: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.293: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.293: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.293: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.294: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.294: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.295: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.295: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.295: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.295: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.295: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.295: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.296: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.296: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.296: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.296: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.297: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.297: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.297: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.297: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.297: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.297: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.298: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.298: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.298: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.299: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.299: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.299: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.299: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.299: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.300: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.300: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.300: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.300: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.301: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.301: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.301: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.301: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.301: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.301: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.302: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.302: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.303: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.303: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.303: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.303: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.303: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.303: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.304: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.304: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.304: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.304: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.304: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.305: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.305: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.305: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.305: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.305: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.306: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.306: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.306: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.306: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.306: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.306: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.307: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.307: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.308: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.308: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.308: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.308: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.308: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.308: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.309: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.309: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.309: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.309: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.310: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.310: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.310: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.310: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.310: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.310: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.311: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.311: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.311: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.311: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.312: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.312: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.312: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.312: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.313: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.313: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.313: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.313: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.313: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.313: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.314: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.314: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.314: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.314: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.315: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.315: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.315: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.315: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.315: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.315: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.316: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.316: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.317: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.317: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.317: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.317: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.317: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.317: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.318: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.318: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.318: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.318: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.318: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.318: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.319: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.319: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.319: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.319: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.319: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.319: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.320: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.320: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.320: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.320: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.320: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.320: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.321: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.321: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.322: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.322: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.322: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.322: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.322: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.322: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.323: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.323: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.323: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.323: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.324: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.324: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.324: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.324: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.324: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.324: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.325: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.325: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.326: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.326: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.326: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.326: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.326: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.326: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.327: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.327: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.327: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.327: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.328: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.328: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.328: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.328: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.328: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.328: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.329: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.329: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.330: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.330: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.330: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.330: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.330: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.330: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.330: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.330: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.331: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.331: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.331: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.331: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.332: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.332: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.332: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.333: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.333: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.333: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.333: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.333: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.334: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.334: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.334: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.334: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.335: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.335: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.335: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.335: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.335: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.335: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.336: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.336: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.336: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.337: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.337: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.337: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.337: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.337: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.338: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.338: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.338: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.338: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.338: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.338: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.339: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.339: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.339: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.339: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.339: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.339: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.340: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.340: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.340: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.340: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.341: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.341: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.341: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.341: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.341: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.341: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.342: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.342: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.342: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.342: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.342: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.342: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.342: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.342: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.343: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.343: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.343: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.343: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.343: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.343: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.344: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.344: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.344: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.345: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.345: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.345: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.345: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.345: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.346: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.346: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.346: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.346: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.346: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.346: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.346: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.347: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.347: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.347: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.347: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.347: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.348: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.348: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.348: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.348: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.348: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.348: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.349: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.349: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.349: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.349: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.349: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.349: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.350: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.350: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.350: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.350: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.350: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.350: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.350: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.350: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.351: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.351: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.351: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.351: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.351: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.351: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.352: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.352: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.352: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.352: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.352: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.352: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.353: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.353: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.353: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.353: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.353: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.353: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.354: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.354: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.354: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.354: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.354: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.354: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.355: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.355: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.355: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.355: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.355: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.355: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.356: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.356: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.356: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.356: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.356: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.356: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.357: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.357: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.358: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.358: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.358: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.358: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.358: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.358: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.359: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.359: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.359: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.359: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.359: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.359: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.360: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.360: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.360: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.360: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.361: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.361: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.361: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.361: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.361: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.361: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.362: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.362: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.363: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.363: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.363: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.363: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.363: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.363: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.364: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.364: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.364: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.364: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.365: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.365: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.365: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.365: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.365: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.365: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.365: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.366: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.366: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.366: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.366: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.366: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.366: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.367: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.367: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.368: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.368: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.368: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.368: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.368: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.368: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.369: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.369: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.369: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.369: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.370: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.370: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.370: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.370: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.370: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.370: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.371: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.371: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.371: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.371: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.371: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.371: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.372: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.372: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.373: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.373: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.373: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.373: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.373: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.373: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.374: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.374: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.374: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.374: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.375: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.375: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.375: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.375: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.375: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.375: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.376: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.376: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.377: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.377: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.377: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.377: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.377: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.377: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.378: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.378: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.378: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.378: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.378: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.379: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.379: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.379: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.379: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.379: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.380: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.380: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.380: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.380: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.380: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.380: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.381: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.381: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.382: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.382: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.382: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.382: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.382: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.382: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.382: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.382: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.383: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.383: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.383: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.383: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.384: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.384: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.384: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.384: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.384: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.384: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.385: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.385: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.386: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.386: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.386: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.386: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.386: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.387: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.387: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.387: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.387: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.387: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.387: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.387: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.388: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.388: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.388: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.389: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.389: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.389: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.389: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.389: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.390: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.390: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.390: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.390: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.391: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.391: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.391: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.391: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.391: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.391: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.391: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.392: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.392: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.393: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.393: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.393: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.393: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.393: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.393: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.394: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.394: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.394: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.394: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.395: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.395: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.396: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.396: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.396: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.396: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.396: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.396: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.397: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.397: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.397: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.397: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.398: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.398: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.398: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.398: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.398: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.398: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.399: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.399: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.399: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.399: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.400: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.400: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.400: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.400: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.401: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.401: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.401: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.401: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.401: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.401: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.402: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.402: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.402: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.402: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.403: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.403: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.403: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.403: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.403: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.403: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.404: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.404: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.405: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.405: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.405: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.405: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.405: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.405: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.406: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.406: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.406: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.406: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.406: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.406: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.406: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.406: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.407: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.407: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.407: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.407: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.408: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.408: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.408: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.408: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.408: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.408: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.409: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.409: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.410: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.410: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.410: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.410: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.410: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.410: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.411: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.411: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.411: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.411: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.412: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.412: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.412: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.412: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.412: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.412: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.413: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.413: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.414: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.414: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.414: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.414: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.414: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.414: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.415: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.415: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.415: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.415: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.416: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.416: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.416: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.416: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.416: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.416: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.417: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.417: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.417: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.417: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.417: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.417: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.418: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.418: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.419: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.419: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.419: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.419: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.419: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.419: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.420: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.420: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.420: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.420: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.420: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.421: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.421: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.421: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.421: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.421: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.422: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.422: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.422: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.422: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.422: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.423: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.423: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.423: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.424: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.424: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.424: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.424: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.424: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.424: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.425: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.425: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.425: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.425: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.426: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.426: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.426: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.426: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.426: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.426: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.427: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.427: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.428: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.428: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.428: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.428: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.428: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.428: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.429: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.429: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.429: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.429: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.430: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.430: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.430: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.430: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.430: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.430: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.431: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.431: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.432: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.432: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.432: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.432: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.432: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.432: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.433: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.433: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.433: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.433: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.433: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.433: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.434: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.434: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.434: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.434: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.435: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.435: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.435: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.436: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.436: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.436: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.436: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.436: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.437: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.437: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.437: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.437: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.437: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.437: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.438: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.438: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.438: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.438: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.438: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.438: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.439: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.439: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.439: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.439: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.439: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.439: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.440: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.440: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.441: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.441: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.441: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.441: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.441: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.441: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.442: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.442: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.442: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.442: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.443: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.443: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.443: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.443: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.443: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.443: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.444: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.444: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.445: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.445: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.445: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.445: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.445: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.445: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.446: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.446: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.446: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.446: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.446: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.446: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.447: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.447: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.447: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.447: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.448: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.448: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.448: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.448: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.448: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.448: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.449: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.449: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.450: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.450: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.450: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.450: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.451: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.451: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.451: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.452: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.452: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.452: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.452: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.452: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.453: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.453: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.453: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.453: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.453: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.453: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.454: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.454: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.454: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.454: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.455: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.455: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.455: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.455: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.455: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.455: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.456: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.456: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.456: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.456: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.456: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.456: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.457: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.457: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.458: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.458: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.458: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.458: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.458: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.458: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.459: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.459: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.459: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.459: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.460: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.460: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.460: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.460: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.460: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.460: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.461: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.461: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.461: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.461: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.461: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.461: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.462: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.462: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.463: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.463: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.463: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.463: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.463: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.463: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.463: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.464: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.464: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.464: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.464: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.464: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.464: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.465: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.465: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.465: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.465: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.466: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.466: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.466: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.466: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.467: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.467: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.467: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.467: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.467: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.467: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.467: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.468: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.468: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.468: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.468: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.469: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.469: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.469: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.469: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.469: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.469: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.470: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.470: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.471: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.471: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.471: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.471: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.471: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.471: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.472: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.472: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.472: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.472: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.472: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.472: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.473: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.473: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.473: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.473: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.473: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.473: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.474: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.474: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.474: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.474: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.474: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.474: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.475: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.475: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.476: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.476: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.476: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.476: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.476: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.476: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.477: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.477: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.477: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.477: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.478: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.478: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.478: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.478: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.478: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.478: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.479: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.479: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.480: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.480: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.480: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.480: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.480: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.480: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.481: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.481: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.481: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.481: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.482: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.482: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.482: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.482: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.482: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.482: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.483: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.483: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.483: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.483: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.483: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.483: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.484: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.484: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.484: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.485: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.485: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.485: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.485: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.485: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.486: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.486: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.486: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.486: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.486: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.486: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.487: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.487: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.487: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.487: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.487: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.488: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.488: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.488: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.488: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.488: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.489: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.489: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.489: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.490: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.490: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.490: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.490: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.490: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.491: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.491: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.491: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.491: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.491: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.491: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.491: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.492: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.492: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.492: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.493: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.493: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.493: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.493: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.493: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.494: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.494: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.495: [vfs7552] CAPTURE_NUM_STATES entering state 4 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.495: Cleaning image 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.495: variance_after = 20 318s 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.495: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.495: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.495: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.496: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.496: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.496: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.496: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.496: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.497: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.497: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.497: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.497: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.497: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.497: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.498: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.498: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.499: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.499: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.499: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.499: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.499: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.499: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.500: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.500: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.500: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.500: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.501: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.501: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.501: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.501: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.501: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.501: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.502: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.502: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.502: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.502: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.502: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.502: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.503: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.503: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.504: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.504: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.504: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.504: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.504: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.504: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.505: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.505: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.505: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.505: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.506: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.506: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.506: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.506: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.506: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.506: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.507: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.507: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.507: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.508: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.508: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.508: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.508: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.508: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.509: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.509: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.509: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.509: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.510: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.510: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.510: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.510: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.510: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.510: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.511: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.511: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.512: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.512: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.512: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.512: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.512: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.512: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.513: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.513: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.513: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.513: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.513: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.513: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.514: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.514: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.514: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.514: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.515: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.515: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.516: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.516: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.516: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.516: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.517: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.517: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.517: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.517: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.517: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.517: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.518: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.518: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.519: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.519: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.519: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.519: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.519: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.519: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.520: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.520: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.520: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.520: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.521: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.521: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.521: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.521: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.521: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.522: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.522: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.522: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.523: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.523: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.523: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.523: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.524: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.524: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.524: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.524: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.524: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.524: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.525: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.525: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.526: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.526: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.526: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.526: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.526: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.526: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.527: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.527: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.527: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.527: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.528: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.528: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.528: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.528: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.528: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.528: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.529: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.529: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.530: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.530: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.530: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.530: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.530: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.530: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.530: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.530: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.531: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.531: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.531: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.531: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.531: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.531: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.532: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.532: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.532: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.532: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.532: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.533: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.533: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.533: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.533: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.533: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.533: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.534: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.534: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.535: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.535: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.535: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.535: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.535: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.535: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.535: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.535: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.536: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.536: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.536: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.536: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.537: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.537: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.537: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.537: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.537: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.537: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.538: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.538: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.539: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.539: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.539: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.539: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.539: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.539: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.540: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.540: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.540: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.540: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.541: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.541: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.541: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.542: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.542: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.542: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.542: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.542: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.543: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.543: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.543: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.543: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.544: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.544: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.544: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.544: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.544: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.544: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.545: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.545: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.545: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.545: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.545: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.545: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.546: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.546: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.547: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.547: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.547: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.547: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.548: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.548: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.548: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.548: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.548: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.548: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.549: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.549: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.550: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.550: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.550: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.550: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.550: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.550: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.551: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.551: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.551: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.551: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.552: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.552: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.552: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.552: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.552: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.552: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.553: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.553: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.553: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.554: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.554: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.554: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.554: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.554: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.555: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.555: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.555: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.555: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.556: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.556: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.556: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.556: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.556: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.556: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.556: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.557: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.557: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.558: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.558: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.558: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.558: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.558: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.558: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.559: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.559: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.559: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.559: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.559: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.560: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.560: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.560: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.560: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.560: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.561: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.561: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.561: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.561: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.561: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.561: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.562: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.562: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.562: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.563: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.563: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.563: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.563: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.563: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.564: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.564: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.564: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.564: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.564: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.564: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.565: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.565: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.565: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.565: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.566: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.566: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.566: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.566: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.566: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.566: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.566: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.567: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.567: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.568: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.568: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.568: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.568: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.568: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.569: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.569: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.569: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.570: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.570: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.570: [vfs7552] CAPTURE_NUM_STATES entering state 4 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.570: Cleaning image 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.571: variance_after = 18 318s 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.571: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.571: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.571: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.571: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.572: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.572: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.572: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.572: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.573: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.573: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.573: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.573: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.573: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.573: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.574: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.574: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.575: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.575: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.575: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.575: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.575: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.575: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.576: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.576: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.576: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.576: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.577: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.577: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.577: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.577: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.577: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.577: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.578: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.578: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.579: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.579: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.579: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.579: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.579: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.579: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.580: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.580: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.581: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.581: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.581: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.581: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.581: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.581: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.582: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.582: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.582: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.582: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.583: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.583: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.583: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.583: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.584: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.584: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.584: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.584: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.585: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.585: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.585: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.585: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.586: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.586: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.586: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.586: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.586: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.586: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.587: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.587: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.588: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.588: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.588: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.588: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.588: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.588: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.589: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.589: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.589: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.589: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.590: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.590: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.590: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.590: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.590: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.590: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.591: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.591: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.592: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.592: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.592: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.592: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.592: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.593: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.593: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.593: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.593: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.593: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.594: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.594: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.595: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.595: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.595: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.595: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.595: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.595: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.596: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.596: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.596: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.596: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.597: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.597: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.598: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.598: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.598: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.598: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.598: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.598: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.599: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.599: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.599: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.599: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.600: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.600: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.600: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.600: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.600: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.600: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.601: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.601: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.602: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.602: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.602: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.602: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.602: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.602: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.603: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.603: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.603: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.603: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.604: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.604: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.605: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.605: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.605: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.605: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.605: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.605: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.606: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.606: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.606: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.606: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.606: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.607: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.607: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.607: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.607: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.607: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.608: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.608: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.608: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.608: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.608: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.608: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.609: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.609: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.610: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.610: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.610: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.610: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.611: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.611: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.611: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.611: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.611: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.611: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.612: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.612: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.612: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.612: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.613: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.613: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.613: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.613: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.614: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.614: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.614: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.614: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.614: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.614: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.615: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.615: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.615: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.615: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.616: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.616: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.616: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.616: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.616: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.616: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.617: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.617: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.617: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.617: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.617: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.617: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.618: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.618: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.619: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.619: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.619: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.619: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.619: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.619: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.620: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.620: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.620: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.620: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.620: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.621: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.621: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.621: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.621: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.621: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.622: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.622: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.622: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.622: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.622: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.622: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.623: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.623: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.624: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.624: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.624: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.624: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.624: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.624: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.625: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.625: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.625: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.625: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.626: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.626: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.626: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.626: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.626: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.626: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.627: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.627: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.628: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.628: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.628: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.628: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.628: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.628: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.629: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.629: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.629: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.629: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.629: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.629: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.630: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.630: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.630: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.630: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.630: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.630: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.630: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.631: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.631: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.631: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.631: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.631: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.632: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.632: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.632: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.632: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.632: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.632: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.633: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.633: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.633: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.633: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.634: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.634: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.634: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.634: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.635: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.635: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.635: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.635: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.635: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.635: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.636: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.636: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.636: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.636: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.636: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.636: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.637: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.637: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.637: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.637: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.637: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.638: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.638: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.638: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.638: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.638: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.639: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.639: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.639: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.639: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.639: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.639: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.640: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.640: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.641: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.641: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.641: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.641: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.641: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.641: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.642: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.642: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.642: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.642: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.643: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.643: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.643: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.643: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.643: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.643: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.643: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.644: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.644: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.644: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.644: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.644: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.645: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.645: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.646: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.646: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.646: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.646: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.646: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.647: [vfs7552] CAPTURE_NUM_STATES entering state 4 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.647: Cleaning image 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.647: variance_after = 18 318s 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.647: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.647: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.648: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.648: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.648: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.648: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.648: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.648: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.649: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.649: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.649: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.649: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.649: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.649: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.650: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.650: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.651: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.651: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.651: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.651: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.651: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.651: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.652: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.652: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.652: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.652: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.653: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.653: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.653: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.653: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.653: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.653: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.654: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.654: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.655: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.655: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.655: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.655: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.655: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.655: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.656: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.656: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.656: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.656: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.656: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.657: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.657: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.657: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.657: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.657: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.658: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.658: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.658: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.658: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.659: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.659: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.659: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.659: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.660: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.660: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.660: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.660: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.660: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.660: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.661: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.661: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.661: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.661: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.661: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.661: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.661: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.662: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.662: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.662: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.662: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.662: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.662: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.663: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.663: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.663: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.663: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.664: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.664: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.664: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.664: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.664: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.664: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.665: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.665: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.665: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.665: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.665: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.665: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.666: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.666: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.666: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.666: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.666: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.666: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.667: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.667: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.667: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.668: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.668: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.668: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.668: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.668: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.669: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.669: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.669: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.669: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.669: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.669: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.670: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.670: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.670: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.670: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.670: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.670: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.671: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.671: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.671: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.671: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.671: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.671: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.672: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.672: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.672: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.672: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.673: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.673: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.673: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.673: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.673: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.673: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.674: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.674: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.674: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.675: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.675: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.675: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.675: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.675: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.676: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.676: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.676: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.676: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.676: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.676: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.677: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.677: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.677: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.677: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.678: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.678: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.678: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.678: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.678: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.678: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.679: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.679: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.679: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.679: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.679: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.680: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.680: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.680: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.681: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.681: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.681: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.681: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.681: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.681: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.682: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.682: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.682: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.682: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.683: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.683: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.683: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.683: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.683: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.683: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.684: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.684: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.685: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.685: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.685: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.685: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.685: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.685: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.686: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.686: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.686: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.686: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.686: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.686: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.687: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.687: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.687: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.687: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.688: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.688: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.688: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.688: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.688: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.688: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.689: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.689: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.689: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.689: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.689: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.689: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.690: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.690: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.690: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.690: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.691: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.691: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.691: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.691: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.692: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.692: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.692: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.692: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.692: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.692: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.693: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.693: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.693: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.693: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.693: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.693: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.694: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.694: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.694: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.694: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.695: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.695: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.695: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.695: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.695: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.695: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.696: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.696: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.696: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.697: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.697: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.697: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.697: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.697: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.698: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.698: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.698: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.698: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.698: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.698: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.699: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.699: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.699: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.699: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.700: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.700: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.700: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.700: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.700: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.700: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.701: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.701: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.701: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.701: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.701: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.701: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.701: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.702: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.702: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.703: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.703: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.703: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.703: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.703: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.703: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.704: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.704: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.704: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.704: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.705: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.705: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.705: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.705: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.705: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.705: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.706: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.706: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.706: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.706: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.706: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.706: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.707: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.707: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.708: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.708: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.708: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.708: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.708: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.708: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.709: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.709: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.709: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.709: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.709: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.709: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.710: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.710: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.710: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.710: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.711: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.711: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.711: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.711: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.711: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.711: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.712: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.712: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.713: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.713: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.713: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.713: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.713: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.713: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.714: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.714: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.714: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.714: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.714: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.714: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.715: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.715: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.715: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.715: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.716: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.716: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.716: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.716: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.716: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.716: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.717: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.717: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.717: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.717: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.717: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.717: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.718: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.718: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.719: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.719: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.719: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.719: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.719: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.719: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.720: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.720: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.720: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.720: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.720: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.720: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.721: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.721: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.721: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.721: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.721: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.722: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.722: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.722: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.722: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.723: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.723: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.723: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.723: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.724: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.724: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.724: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.724: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.724: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.724: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.725: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.725: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.725: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.725: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.726: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.726: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.726: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.727: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.727: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.727: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.727: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.727: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.728: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.728: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.728: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.728: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.728: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.728: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.729: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.729: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.729: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.729: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.730: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.730: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.730: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.730: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.730: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.730: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.731: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.731: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.732: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.732: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.732: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.732: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.732: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.732: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.733: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.733: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.733: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.733: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.734: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.734: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.734: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.734: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.734: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.734: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.735: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.735: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.736: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.736: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.736: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.736: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.736: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.736: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.737: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.737: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.737: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.737: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.738: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.738: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.738: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.739: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.739: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.739: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.739: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.739: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.740: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.740: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.740: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.740: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.740: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.741: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.741: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.741: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.741: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.741: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.742: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.742: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.743: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.743: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.743: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.743: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.743: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.743: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.744: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.744: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.744: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.744: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.745: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.745: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.745: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.745: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.746: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.746: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.746: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.746: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.747: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.747: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.747: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.747: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.747: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.748: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.748: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.748: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.748: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.748: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.749: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.749: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.749: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.749: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.749: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.749: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.750: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.750: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.751: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.751: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.751: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.751: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.751: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.751: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.752: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.752: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.752: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.752: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.753: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.753: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.753: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.754: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.754: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.754: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.754: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.754: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.755: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.755: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.755: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.755: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.755: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.755: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.756: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.756: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.756: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.756: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.757: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.757: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.757: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.758: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.758: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.758: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.758: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.758: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.759: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.759: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.759: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.759: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.759: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.759: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.759: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.759: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.760: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.760: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.760: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.760: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.760: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.761: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.761: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.761: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.762: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.762: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.762: [vfs7552] CAPTURE_NUM_STATES entering state 4 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.762: Cleaning image 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.762: variance_after = 18 318s 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.762: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.763: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.763: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.763: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.764: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.764: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.764: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.764: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.764: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.764: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.765: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.765: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.765: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.765: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.766: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.766: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.766: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.766: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.766: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.766: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.767: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.767: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.768: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.768: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.768: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.768: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.768: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.768: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.769: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.769: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.769: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.769: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.769: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.769: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.770: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.770: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.770: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.770: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.770: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.770: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.771: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.771: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.771: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.771: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.772: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.772: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.772: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.772: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.772: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.772: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.773: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.773: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.773: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.773: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.773: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.773: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.774: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.774: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.775: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.775: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.775: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.775: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.775: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.776: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.776: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.776: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.776: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.776: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.777: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.777: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.777: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.777: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.777: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.777: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.778: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.778: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.778: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.778: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.778: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.779: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.779: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.779: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.780: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.780: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.780: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.780: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.780: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.780: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.780: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.780: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.781: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.781: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.781: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.781: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.781: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.781: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.782: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.782: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.782: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.782: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.782: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.782: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.783: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.783: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.783: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.783: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.783: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.784: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.784: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.784: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.784: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.784: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.785: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.785: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.785: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.785: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.785: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.785: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.786: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.786: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.787: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.787: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.787: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.787: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.787: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.787: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.788: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.788: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.788: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.788: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.788: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.788: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.789: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.789: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.789: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.789: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.790: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.790: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.790: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.790: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.790: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.790: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.791: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.791: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.791: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.791: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.792: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.792: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.792: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.792: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.793: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.793: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.793: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.793: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.793: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.793: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.794: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.794: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.794: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.794: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.795: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.795: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.795: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.795: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.795: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.795: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.796: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.796: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.796: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.796: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.796: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.796: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.797: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.797: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.798: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.798: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.798: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.798: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.798: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.798: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.799: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.799: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.799: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.799: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.800: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.800: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.800: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.800: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.800: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.800: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.801: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.801: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.801: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.802: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.802: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.802: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.802: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.802: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.803: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.803: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.803: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.803: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.803: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.803: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.804: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.804: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.804: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.804: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.805: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.805: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.805: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.805: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.805: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.805: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.806: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.806: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.806: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.806: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.806: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.806: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.807: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.807: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.808: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.808: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.808: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.808: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.808: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.808: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.809: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.809: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.809: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.809: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.810: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.810: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.810: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.810: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.810: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.810: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.810: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.810: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.811: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.811: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.811: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.811: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.811: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.811: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.812: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.812: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.812: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.812: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.812: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.812: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.813: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.813: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.813: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.813: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.814: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.814: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.814: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.814: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.815: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.815: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.815: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.815: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.815: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.815: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.816: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.816: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.816: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.816: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.816: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.816: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.817: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.817: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.817: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.817: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.817: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.817: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.818: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.818: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.818: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.818: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.818: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.818: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.819: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.819: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.819: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.819: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.820: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.820: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.820: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.820: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.820: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.820: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.821: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.821: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.821: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.821: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.821: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.821: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.822: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.822: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.823: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.823: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.823: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.823: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.823: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.823: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.824: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.824: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.824: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.824: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.824: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.824: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.825: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.825: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.825: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.825: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.825: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.825: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.825: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.825: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.826: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.826: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.826: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.826: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.827: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.827: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.827: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.827: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.827: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.827: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.828: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.828: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.828: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.828: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.828: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.828: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.829: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.829: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.829: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.829: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.829: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.829: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.830: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.830: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.830: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.830: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.830: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.830: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.831: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.831: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.831: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.832: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.832: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.832: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.832: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.832: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.832: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.833: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.833: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.833: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.833: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.833: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.834: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.834: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.834: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.834: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.834: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.834: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.835: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.835: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.835: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.835: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.836: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.836: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.836: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.836: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.836: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.836: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.837: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.837: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.837: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.837: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.837: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.837: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.838: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.838: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.838: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.838: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.838: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.838: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.839: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.839: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.839: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.840: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.840: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.840: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.840: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.840: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.841: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.841: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.841: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.841: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.841: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.841: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.842: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.842: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.842: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.842: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.842: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.842: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.843: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.843: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.843: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.843: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.843: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.843: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.844: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.844: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.844: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.844: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.844: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.844: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.845: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.845: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.845: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.845: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.846: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.846: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.846: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.846: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.846: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.846: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.847: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.847: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.847: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.847: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.847: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.847: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.848: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.848: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.848: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.849: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.849: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.849: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.849: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.849: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.850: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.850: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.850: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.850: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.850: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.850: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.851: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.851: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.851: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.851: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.851: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.851: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.852: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.852: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.852: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.852: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.852: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.852: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.853: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.853: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.853: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.853: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.854: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.854: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.854: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.854: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.854: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.854: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.855: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.855: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.855: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.855: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.856: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.856: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.856: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.856: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.857: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.857: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.857: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.857: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.857: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.857: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.857: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.857: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.858: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.858: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.858: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.858: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.858: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.858: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.859: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.859: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.859: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.859: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.859: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.859: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.860: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.860: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.860: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.860: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.860: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.861: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.861: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.861: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.861: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.861: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.862: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.862: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.862: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.862: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.862: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.862: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.862: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.863: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.863: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.863: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.863: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.863: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.863: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.864: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.864: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.864: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.864: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.864: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.864: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.865: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.865: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.866: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.866: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.866: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.866: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.866: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.866: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.867: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.867: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.867: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.867: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.867: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.867: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.868: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.868: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.868: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.868: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.869: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.869: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.869: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.869: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.869: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.869: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.869: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.869: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.870: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.870: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.870: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.870: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.870: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.870: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.871: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.871: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.872: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.872: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.872: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.872: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.872: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.872: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.873: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.873: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.873: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.873: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.873: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.873: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.874: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.874: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.874: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.874: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.874: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.874: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.875: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.875: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.875: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.875: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.875: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.875: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.876: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.876: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.876: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.876: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.876: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.876: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.877: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.877: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.877: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.877: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.877: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.877: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.878: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.878: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.878: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.878: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.879: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.879: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.879: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.879: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.880: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.880: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.880: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.880: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.880: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.880: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.880: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.881: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.881: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.881: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.881: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.881: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.882: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.882: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.882: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.883: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.883: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.883: [vfs7552] CAPTURE_NUM_STATES entering state 4 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.883: Cleaning image 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.883: variance_after = 18 318s 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.883: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.883: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.884: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.884: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.884: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.884: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.884: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.884: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.885: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.885: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.885: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.886: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.886: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.886: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.886: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.886: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.886: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.886: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.887: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.887: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.887: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.887: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.887: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.887: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.888: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.888: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.888: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.888: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.889: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.889: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.889: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.889: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.889: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.889: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.890: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.890: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.890: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.890: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.890: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.890: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.891: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.891: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.892: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.892: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.892: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.892: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.892: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.892: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.892: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.892: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.893: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.893: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.893: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.893: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.893: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.893: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.894: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.894: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.894: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.894: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.894: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.894: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.895: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.895: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.895: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.895: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.895: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.895: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.896: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.896: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.896: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.896: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.897: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.897: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.897: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.897: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.897: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.897: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.898: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.898: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.898: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.898: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.898: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.898: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.898: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.898: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.899: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.899: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.900: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.900: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.900: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.900: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.900: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.900: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.901: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.901: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.901: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.901: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.901: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.901: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.902: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.902: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.902: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.902: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.903: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.903: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.903: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.903: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.903: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.903: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.903: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.903: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.904: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.904: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.905: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.905: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.905: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.905: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.905: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.905: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.906: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.906: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.906: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.906: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.906: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.906: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.907: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.907: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.907: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.907: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.907: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.908: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.908: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.908: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.908: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.908: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.908: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.908: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.908: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.909: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.909: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.909: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.909: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.909: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.909: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.909: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.909: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.910: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.910: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.911: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.911: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.911: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.911: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.911: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.911: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.911: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.912: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.912: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.912: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.912: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.912: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.912: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.913: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.913: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.913: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.913: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.913: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.913: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.913: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.913: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.914: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.914: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.914: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.914: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.915: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.915: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.915: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.915: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.915: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.915: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.916: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.916: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.916: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.916: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.916: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.917: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.917: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.917: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.918: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.918: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.918: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.918: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.918: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.918: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.919: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.919: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.919: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.919: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.919: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.919: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.920: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.920: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.920: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.920: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.920: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.920: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.920: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.920: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.921: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.921: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.921: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.921: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.922: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.922: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.922: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.922: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.922: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.922: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.923: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.923: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.923: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.923: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.923: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.923: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.924: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.924: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.925: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.925: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.925: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.925: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.925: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.925: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.925: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.925: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.926: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.926: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.926: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.926: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.926: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.926: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.927: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.927: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.927: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.927: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.927: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.927: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.928: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.928: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.928: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.928: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.928: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.928: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.929: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.929: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.929: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.929: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.930: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.930: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.930: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.930: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.930: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.930: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.931: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.931: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.932: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.932: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.932: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.932: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.932: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.932: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.933: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.933: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.933: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.933: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.933: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.933: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.934: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.934: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.934: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.934: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.934: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.934: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.934: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.935: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.935: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.935: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.936: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.936: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.936: [vfs7552] CAPTURE_NUM_STATES entering state 2 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.936: [vfs7552] REQUEST CHUNK entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.936: Sending vfs7552_read_image_chunk 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.937: [vfs7552] REQUEST CHUNK completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.937: [vfs7552] CAPTURE_NUM_STATES entering state 3 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.937: [vfs7552] CAPTURE_NUM_STATES entering state 4 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.938: Cleaning image 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.938: variance_after = 17 318s 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.938: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.938: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.938: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.938: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.939: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.939: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.939: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.939: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.939: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.939: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.940: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.940: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.940: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.940: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.940: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.940: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.941: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.941: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.941: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.941: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.941: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.941: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.942: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.942: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.942: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.942: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.942: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.942: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.943: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.943: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.943: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.943: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.943: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.943: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.944: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.944: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.944: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.944: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.945: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.945: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.945: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.945: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.946: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.946: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.946: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.946: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.946: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.946: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.947: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.947: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.947: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.947: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.947: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.947: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.948: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.948: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.948: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.948: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.948: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.948: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.949: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.949: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.949: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.949: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.949: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.949: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.950: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.950: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.950: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.950: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.951: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.951: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.951: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.951: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.951: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.951: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.951: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.951: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.952: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.952: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.952: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.952: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.952: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.952: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.953: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.953: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.954: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.954: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.954: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.954: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.954: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.954: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.955: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.955: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.955: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.955: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.955: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.955: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.956: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.956: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.956: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.956: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.957: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.957: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.957: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.957: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.957: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.957: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.958: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.958: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.958: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.958: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.958: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.958: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.959: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.959: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.959: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.959: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.959: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.959: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.960: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.960: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.961: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.961: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.961: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.961: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.961: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.961: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.961: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.961: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.962: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.962: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.962: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.962: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.963: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.963: Receiving 64 bytes 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.963: Got 6 bytes out of 64 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.963: [vfs7552] QUERY DATA READY completed successfully 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.963: [vfs7552] QUERY DATA READY entering state 0 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.963: Sending vfs7552_is_image_ready 318s (process:2572): libfprint-SSM-DEBUG: 05:02:17.964: [vfs7552] QUERY DATA READY entering state 1 318s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.964: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.964: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.964: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.964: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.964: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.964: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.965: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.965: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.966: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.966: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.966: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.966: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.966: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.966: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.966: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.966: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.967: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.967: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.967: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.967: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.967: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.967: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.967: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.968: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.968: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.968: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.968: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.968: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.968: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.968: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.968: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.969: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.969: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.969: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.969: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.970: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.970: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.970: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.970: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.970: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.970: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.971: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.971: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.971: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.971: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.971: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.971: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.972: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.972: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.972: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.972: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.972: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.972: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.973: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.973: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.973: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.974: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.974: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.974: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.974: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.974: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.975: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.975: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.975: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.975: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.975: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.975: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.975: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.975: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.976: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.976: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.976: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.976: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.976: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.976: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.977: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.977: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.977: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.977: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.978: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.978: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.978: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.978: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.978: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.978: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.979: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.979: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.979: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.979: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.979: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.979: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.980: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.980: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.980: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.980: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.980: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.980: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.981: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.981: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.981: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.981: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.982: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.982: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.982: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.982: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.982: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.983: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.983: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.983: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.983: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.983: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.983: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.983: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.984: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.984: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.984: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.984: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.984: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.984: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.985: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.985: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.985: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.985: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.985: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.985: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.986: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.986: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.986: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.986: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.986: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.986: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.987: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.987: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.987: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.987: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.987: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.987: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.987: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.988: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.988: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.988: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.989: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.989: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.989: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.989: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.989: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.990: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.990: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.990: [vfs7552] CAPTURE_NUM_STATES entering state 4 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.990: Cleaning image 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.990: variance_after = 16 319s 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.990: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.991: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.991: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.991: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.991: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.992: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.992: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.992: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.992: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.992: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.993: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.993: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.993: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.993: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.993: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.993: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.994: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.994: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.994: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.994: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.994: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.994: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.995: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.995: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.995: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.995: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.995: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.995: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.996: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.996: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.996: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.996: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.997: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.997: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.997: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.997: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.997: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.997: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.998: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.998: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.998: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.998: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.998: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.998: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:17.999: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:17.999: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.000: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.000: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.000: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.000: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.000: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.000: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.001: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.001: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.001: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.001: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.001: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.001: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.002: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.002: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.002: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.002: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.002: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.002: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.003: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.003: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.003: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.003: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.003: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.003: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.004: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.004: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.004: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.004: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.005: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.005: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.005: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.005: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.005: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.005: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.006: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.006: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.006: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.006: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.006: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.006: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.007: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.007: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.008: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.008: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.008: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.008: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.008: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.008: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.009: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.009: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.009: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.009: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.009: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.009: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.010: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.010: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.010: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.010: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.010: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.010: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.011: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.011: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.011: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.011: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.012: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.012: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.012: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.012: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.012: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.012: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.013: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.013: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.013: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.013: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.013: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.013: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.014: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.014: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.015: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.015: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.015: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.015: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.015: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.015: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.016: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.016: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.016: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.016: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.016: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.016: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.017: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.017: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.017: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.017: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.017: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.017: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.017: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.017: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.018: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.018: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.018: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.018: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.019: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.019: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.019: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.019: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.019: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.019: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.020: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.020: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.020: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.020: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.020: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.020: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.021: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.021: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.021: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.021: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.021: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.021: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.022: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.022: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.023: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.023: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.023: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.023: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.023: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.023: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.024: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.024: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.024: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.024: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.024: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.025: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.025: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.025: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.025: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.025: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.026: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.026: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.026: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.026: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.026: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.026: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.027: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.027: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.027: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.027: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.027: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.027: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.027: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.027: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.028: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.028: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.028: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.028: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.028: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.028: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.029: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.029: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.029: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.030: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.030: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.030: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.030: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.030: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.031: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.031: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.031: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.031: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.031: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.031: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.032: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.032: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.032: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.032: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.032: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.033: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.033: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.033: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.033: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.033: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.034: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.034: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.034: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.034: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.034: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.034: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.035: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.035: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.036: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.036: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.036: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.036: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.036: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.036: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.037: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.037: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.037: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.037: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.038: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.038: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.038: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.038: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.038: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.038: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.039: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.039: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.040: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.040: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.040: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.040: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.040: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.040: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.041: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.041: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.041: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.041: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.041: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.041: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.042: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.042: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.042: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.043: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.043: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.043: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.043: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.044: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.044: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.044: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.044: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.044: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.045: [vfs7552] CAPTURE_NUM_STATES entering state 4 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.045: Cleaning image 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.045: variance_after = 17 319s 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.045: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.045: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.046: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.046: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.046: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.046: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.046: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.046: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.046: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.046: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.047: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.047: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.048: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.048: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.048: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.048: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.048: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.048: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.049: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.049: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.049: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.049: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.050: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.050: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.050: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.050: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.050: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.050: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.051: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.051: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.052: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.052: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.052: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.052: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.052: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.052: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.053: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.053: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.053: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.053: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.054: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.054: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.054: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.054: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.054: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.054: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.055: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.055: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.056: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.056: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.056: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.056: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.056: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.056: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.057: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.057: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.057: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.057: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.058: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.058: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.058: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.058: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.058: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.058: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.059: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.059: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.060: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.060: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.060: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.060: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.060: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.060: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.060: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.060: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.061: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.061: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.061: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.061: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.061: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.061: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.062: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.062: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.062: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.062: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.063: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.063: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.063: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.063: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.063: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.063: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.064: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.064: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.065: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.065: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.065: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.065: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.065: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.065: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.065: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.065: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.066: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.066: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.066: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.066: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.067: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.067: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.067: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.067: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.067: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.067: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.068: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.068: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.069: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.069: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.069: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.069: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.069: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.069: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.070: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.070: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.070: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.070: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.070: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.070: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.071: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.071: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.071: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.071: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.072: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.072: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.072: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.072: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.072: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.072: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.072: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.072: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.073: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.073: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.074: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.074: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.074: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.074: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.074: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.074: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.075: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.075: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.075: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.075: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.075: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.075: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.076: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.076: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.076: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.076: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.076: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.076: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.077: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.077: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.077: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.077: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.077: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.077: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.078: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.078: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.078: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.078: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.078: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.078: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.079: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.079: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.079: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.079: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.079: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.079: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.080: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.080: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.081: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.081: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.081: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.081: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.081: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.081: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.082: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.082: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.082: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.082: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.082: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.082: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.082: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.082: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.083: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.083: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.083: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.083: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.084: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.084: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.084: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.084: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.084: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.084: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.085: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.085: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.085: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.085: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.085: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.085: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.085: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.085: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.086: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.086: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.086: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.087: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.087: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.087: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.087: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.087: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.088: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.088: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.088: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.088: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.088: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.088: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.089: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.089: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.089: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.089: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.089: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.089: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.090: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.090: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.090: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.090: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.090: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.090: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.091: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.091: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.091: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.091: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.091: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.091: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.092: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.092: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.093: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.093: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.093: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.093: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.093: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.093: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.094: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.094: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.094: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.094: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.094: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.094: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.095: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.095: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.095: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.095: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.095: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.096: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.096: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.096: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.096: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.096: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.096: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.096: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.097: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.097: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.097: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.097: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.097: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.097: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.098: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.098: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.099: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.099: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.099: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.099: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.099: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.099: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.100: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.100: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.100: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.100: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.100: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.100: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.101: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.101: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.101: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.101: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.101: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.101: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.101: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.101: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.102: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.102: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.102: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.102: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.103: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.103: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.103: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.103: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.103: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.103: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.104: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.104: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.104: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.104: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.104: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.104: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.104: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.105: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.105: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.105: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.106: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.106: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.106: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.106: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.107: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.107: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.107: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.107: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.107: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.108: [vfs7552] CAPTURE_NUM_STATES entering state 4 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.108: Cleaning image 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.108: variance_after = 17 319s 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.108: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.108: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.109: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.109: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.109: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.109: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.109: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.109: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.110: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.110: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.110: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.110: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.110: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.110: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.111: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.111: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.111: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.111: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.111: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.111: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.112: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.112: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.112: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.112: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.112: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.112: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.113: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.113: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.113: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.113: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.114: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.114: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.114: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.114: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.115: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.115: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.115: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.115: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.115: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.115: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.116: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.116: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.116: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.116: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.116: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.116: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.117: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.117: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.117: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.117: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.117: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.117: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.117: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.117: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.118: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.118: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.118: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.118: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.119: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.119: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.120: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.120: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.120: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.120: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.121: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.121: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.121: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.121: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.121: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.121: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.121: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.121: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.122: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.122: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.123: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.123: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.123: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.123: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.123: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.123: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.124: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.124: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.124: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.124: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.125: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.125: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.126: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.126: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.126: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.126: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.126: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.126: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.126: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.126: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.127: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.127: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.127: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.127: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.128: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.128: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.128: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.129: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.129: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.129: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.129: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.129: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.130: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.130: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.130: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.130: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.130: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.130: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.131: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.131: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.131: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.131: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.131: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.131: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.132: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.132: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.132: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.132: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.132: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.132: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.133: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.133: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.133: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.133: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.133: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.133: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.134: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.134: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.135: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.135: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.135: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.135: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.135: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.135: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.136: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.136: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.136: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.136: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.136: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.136: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.136: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.136: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.137: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.137: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.137: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.137: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.138: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.138: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.138: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.138: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.138: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.138: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.139: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.139: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.140: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.140: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.140: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.140: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.140: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.140: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.141: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.141: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.141: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.141: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.142: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.142: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.142: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.142: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.142: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.142: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.142: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.142: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.143: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.143: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.144: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.144: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.144: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.144: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.144: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.144: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.145: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.145: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.145: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.145: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.146: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.146: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.147: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.147: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.147: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.147: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.147: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.147: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.148: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.148: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.148: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.148: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.149: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.149: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.149: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.149: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.149: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.149: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.150: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.150: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.151: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.151: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.151: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.151: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.151: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.151: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.152: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.152: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.152: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.152: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.153: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.153: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.154: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.154: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.154: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.154: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.154: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.154: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.155: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.155: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.155: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.155: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.155: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.155: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.156: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.156: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.156: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.156: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.156: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.156: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.157: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.157: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.157: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.157: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.157: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.158: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.158: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.158: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.158: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.158: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.158: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.158: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.159: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.159: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.159: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.159: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.159: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.159: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.160: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.160: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.160: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.160: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.160: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.160: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.161: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.161: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.161: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.162: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.162: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.162: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.162: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.162: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.163: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.163: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.163: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.163: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.163: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.163: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.164: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.164: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.164: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.164: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.164: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.165: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.165: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.165: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.165: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.165: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.165: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.166: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.166: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.166: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.166: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.166: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.166: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.166: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.166: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.167: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.167: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.167: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.167: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.167: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.167: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.167: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.167: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.168: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.168: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.168: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.168: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.168: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.168: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.168: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.168: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.169: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.169: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.170: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.170: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.170: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.170: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.170: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.170: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.171: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.171: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.171: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.171: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.171: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.171: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.172: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.172: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.172: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.172: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.172: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.172: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.173: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.173: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.173: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.173: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.174: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.174: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.174: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.174: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.174: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.174: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.175: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.175: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.175: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.175: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.175: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.175: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.175: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.175: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.176: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.176: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.177: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.177: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.177: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.177: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.177: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.177: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.178: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.178: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.178: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.178: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.178: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.178: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.179: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.179: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.179: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.179: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.179: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.179: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.180: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.180: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.180: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.180: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.180: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.180: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.181: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.181: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.181: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.181: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.182: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.182: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.182: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.182: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.182: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.183: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.183: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.183: [vfs7552] CAPTURE_NUM_STATES entering state 4 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.183: Cleaning image 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.183: variance_after = 17 319s 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.183: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.184: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.184: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.184: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.185: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.185: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.185: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.185: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.185: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.185: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.186: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.186: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.186: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.186: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.186: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.186: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.187: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.187: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.187: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.187: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.187: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.188: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.188: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.188: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.188: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.188: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.189: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.189: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.189: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.189: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.189: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.189: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.189: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.189: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.190: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.190: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.190: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.190: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.190: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.190: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.191: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.191: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.192: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.192: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.192: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.192: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.192: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.192: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.193: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.193: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.193: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.193: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.193: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.193: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.194: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.194: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.194: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.194: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.194: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.194: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.194: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.194: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.195: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.195: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.195: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.195: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.196: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.196: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.196: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.196: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.196: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.196: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.197: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.197: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.198: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.198: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.198: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.198: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.198: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.198: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.199: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.199: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.199: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.199: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.200: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.200: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.200: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.200: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.201: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.201: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.201: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.201: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.202: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.202: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.202: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.202: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.203: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.203: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.203: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.203: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.203: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.203: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.204: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.204: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.204: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.204: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.205: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.205: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.205: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.205: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.206: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.206: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.206: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.206: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.206: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.206: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.207: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.207: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.207: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.207: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.207: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.207: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.208: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.208: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.208: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.208: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.208: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.208: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.209: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.209: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.209: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.209: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.210: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.210: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.210: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.210: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.210: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.210: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.211: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.211: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.211: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.212: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.212: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.212: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.212: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.212: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.213: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.213: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.213: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.213: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.213: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.213: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.213: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.213: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.214: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.214: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.214: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.214: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.214: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.214: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.215: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.215: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.215: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.215: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.216: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.216: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.216: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.216: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.216: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.216: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.217: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.217: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.217: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.218: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.218: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.218: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.218: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.218: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.219: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.219: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.219: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.219: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.219: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.219: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.220: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.220: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.220: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.220: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.220: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.220: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.221: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.221: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.221: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.221: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.222: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.222: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.222: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.222: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.222: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.222: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.223: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.223: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.223: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.223: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.223: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.223: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.224: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.224: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.225: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.225: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.225: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.225: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.225: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.225: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.226: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.226: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.226: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.226: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.226: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.226: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.227: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.227: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.227: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.227: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.228: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.228: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.228: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.228: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.228: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.228: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.229: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.229: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.229: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.229: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.229: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.229: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.229: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.229: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.230: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.230: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.230: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.230: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.231: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.231: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.231: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.231: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.232: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.232: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.232: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.232: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.232: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.232: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.233: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.233: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.233: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.233: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.233: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.233: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.234: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.234: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.234: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.234: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.235: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.235: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.235: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.235: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.235: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.235: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.235: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.235: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.236: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.236: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.236: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.236: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.236: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.236: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.237: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.237: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.237: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.237: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.237: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.237: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.238: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.238: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.238: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.238: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.238: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.238: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.239: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.239: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.239: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.239: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.239: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.239: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.240: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.240: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.240: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.240: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.241: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.241: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.241: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.241: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.242: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.242: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.242: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.242: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.242: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.242: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.242: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.242: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.243: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.243: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.243: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.243: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.243: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.243: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.244: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.244: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.244: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.244: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.244: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.245: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.245: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.245: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.245: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.245: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.246: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.246: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.246: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.246: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.246: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.246: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.247: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.247: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.247: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.247: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.247: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.247: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.248: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.248: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.248: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.248: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.248: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.248: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.249: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.249: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.250: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.250: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.250: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.250: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.250: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.250: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.250: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.250: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.251: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.251: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.251: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.251: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.251: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.251: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.252: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.252: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.252: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.252: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.252: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.252: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.253: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.253: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.253: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.253: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.254: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.254: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.254: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.254: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.254: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.254: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.255: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.255: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.256: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.256: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.256: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.256: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.256: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.256: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.257: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.257: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.257: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.257: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.257: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.258: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.258: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.258: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.258: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.258: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.258: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.258: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.259: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.259: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.259: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.259: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.259: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.259: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.260: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.260: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.260: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.261: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.261: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.261: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.261: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.261: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.261: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.262: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.262: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.262: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.262: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.262: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.263: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.263: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.263: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.263: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.263: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.263: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.264: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.264: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.264: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.264: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.264: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.264: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.264: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.265: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.265: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.265: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.265: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.265: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.266: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.266: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.266: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.266: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.266: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.266: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.267: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.267: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.268: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.268: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.268: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.268: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.268: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.268: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.269: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.269: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.269: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.269: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.269: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.269: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.269: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.270: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.270: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.270: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.270: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.270: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.271: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.271: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.271: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.271: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.271: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.271: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.272: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.272: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.273: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.273: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.273: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.273: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.273: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.273: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.273: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.273: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.274: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.274: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.274: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.274: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.275: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.275: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.275: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.275: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.275: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.275: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.276: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.276: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.276: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.277: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.277: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.277: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.277: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.277: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.278: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.278: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.278: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.278: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.278: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.278: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.279: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.279: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.279: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.279: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.279: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.279: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.280: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.280: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.280: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.280: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.281: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.281: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.281: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.281: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.282: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.282: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.282: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.282: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.283: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.283: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.283: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.283: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.283: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.283: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.284: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.284: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.284: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.284: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.284: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.284: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.285: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.285: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.285: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.285: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.285: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.285: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.286: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.286: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.287: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.287: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.287: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.287: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.287: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.287: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.288: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.288: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.288: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.288: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.289: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.289: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.289: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.289: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.290: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.290: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.290: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.290: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.291: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.291: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.291: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.291: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.291: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.291: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.292: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.292: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.292: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.292: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.292: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.292: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.293: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.293: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.294: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.294: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.294: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.294: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.295: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.295: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.295: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.295: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.295: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.295: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.296: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.296: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.296: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.297: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.297: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.297: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.297: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.297: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.298: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.298: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.298: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.298: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.298: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.298: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.299: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.299: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.299: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.299: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.299: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.299: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.300: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.300: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.300: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.300: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.300: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.300: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.301: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.301: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.302: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.302: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.302: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.302: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.302: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.302: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.303: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.303: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.303: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.303: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.303: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.303: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.304: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.304: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.304: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.304: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.304: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.304: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.305: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.305: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.306: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.306: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.306: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.306: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.306: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.306: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.306: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.306: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.307: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.307: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.307: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.307: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.307: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.307: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.308: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.308: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.308: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.308: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.309: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.309: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.309: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.309: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.309: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.309: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.309: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.309: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.310: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.310: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.310: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.310: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.310: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.310: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.311: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.311: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.311: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.312: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.312: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.312: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.312: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.312: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.313: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.313: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.313: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.313: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.313: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.313: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.313: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.313: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.314: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.314: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.314: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.314: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.314: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.314: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.315: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.315: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.315: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.315: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.315: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.316: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.316: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.316: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.316: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.316: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.316: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.316: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.317: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.317: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.317: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.317: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.317: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.317: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.318: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.318: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.318: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.318: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.318: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.318: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.319: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.319: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.320: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.320: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.320: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.320: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.320: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.320: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.321: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.321: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.321: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.321: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.321: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.322: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.322: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.322: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.322: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.322: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.323: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.323: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.323: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.323: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.323: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.323: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.324: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.324: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.324: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.325: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.325: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.325: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.325: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.325: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.325: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.325: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.326: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.326: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.326: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.326: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.326: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.326: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.327: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.327: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.327: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.327: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.327: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.327: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.328: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.328: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.328: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.328: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.329: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.329: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.329: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.329: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.329: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.329: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.330: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.330: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.331: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.331: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.331: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.331: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.331: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.331: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.332: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.332: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.332: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.332: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.332: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.333: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.333: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.333: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.333: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.333: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.334: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.334: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.335: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.335: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.335: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.335: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.335: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.335: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.335: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.336: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.336: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.336: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.336: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.336: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.337: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.337: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.337: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.337: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.337: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.337: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.338: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.338: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.339: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.339: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.339: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.339: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.339: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.339: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.339: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.340: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.340: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.340: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.340: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.340: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.340: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.341: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.341: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.341: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.341: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.341: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.341: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.341: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.341: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.342: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.342: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.343: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.343: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.343: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.343: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.343: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.343: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.343: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.343: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.344: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.344: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.344: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.344: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.344: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.345: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.345: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.345: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.345: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.345: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.345: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.346: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.346: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.347: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.347: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.347: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.347: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.347: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.347: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.347: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.347: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.348: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.348: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.348: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.348: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.349: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.349: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.349: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.349: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.349: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.349: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.350: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.350: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.351: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.351: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.351: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.351: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.351: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.351: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.352: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.352: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.352: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.352: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.353: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.353: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.353: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.353: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.353: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.353: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.354: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.354: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.355: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.355: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.355: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.355: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.355: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.355: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.356: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.356: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.356: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.356: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.357: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.357: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.357: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.357: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.357: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.357: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.358: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.358: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.358: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.359: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.359: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.359: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.359: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.359: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.360: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.360: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.360: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.360: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.360: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.360: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.360: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.360: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.361: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.361: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.361: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.361: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.362: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.362: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.362: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.362: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.362: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.362: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.363: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.363: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.363: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.363: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.363: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.363: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.364: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.364: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.365: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.365: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.365: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.365: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.365: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.365: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.365: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.365: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.366: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.366: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.366: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.366: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.366: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.367: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.367: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.367: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.368: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.368: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.368: [vfs7552] CAPTURE_NUM_STATES entering state 4 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.368: Cleaning image 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.368: variance_after = 20 319s 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.368: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.368: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.369: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.369: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.370: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.370: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.370: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.370: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.370: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.370: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.370: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.370: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.371: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.371: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.371: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.371: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.372: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.372: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.372: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.372: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.372: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.372: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.372: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.372: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.373: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.373: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.374: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.374: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.374: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.374: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.374: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.374: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.374: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.374: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.375: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.375: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.375: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.375: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.375: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.376: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.376: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.376: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.376: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.376: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.377: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.377: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.377: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.378: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.378: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.378: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.378: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.378: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.378: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.378: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.379: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.379: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.379: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.379: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.379: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.379: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.380: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.380: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.380: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.380: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.381: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.381: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.381: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.381: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.381: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.381: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.382: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.382: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.383: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.383: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.383: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.383: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.383: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.383: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.384: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.384: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.384: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.384: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.384: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.384: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.385: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.385: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.385: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.385: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.386: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.386: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.386: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.386: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.386: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.386: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.387: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.387: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.388: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.388: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.388: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.388: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.388: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.388: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.389: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.389: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.389: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.389: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.389: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.389: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.390: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.390: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.390: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.390: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.391: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.391: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.391: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.391: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.391: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.391: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.391: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.392: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.392: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.393: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.393: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.393: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.393: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.393: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.393: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.394: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.394: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.394: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.394: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.394: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.394: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.394: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.394: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.395: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.395: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.395: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.395: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.396: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.396: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.396: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.396: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.396: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.396: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.397: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.397: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.398: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.398: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.398: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.398: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.398: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.398: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.399: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.399: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.399: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.399: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.399: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.399: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.399: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.400: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.400: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.400: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.400: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.400: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.401: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.401: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.401: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.401: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.401: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.401: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.402: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.402: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.403: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.403: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.403: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.403: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.403: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.403: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.404: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.404: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.404: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.404: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.405: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.405: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.405: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.405: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.405: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.405: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.406: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.406: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.407: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.407: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.407: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.407: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.407: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.407: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.408: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.408: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.408: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.408: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.408: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.409: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.409: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.409: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.409: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.409: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.410: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.410: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.411: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.411: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.411: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.411: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.411: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.411: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.412: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.412: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.412: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.412: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.412: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.412: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.412: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.412: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.413: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.413: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.413: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.413: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.413: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.413: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.414: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.414: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.414: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.414: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.415: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.415: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.415: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.415: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.415: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.415: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.416: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.416: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.416: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.416: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.416: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.416: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.417: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.417: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.417: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.417: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.417: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.417: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.418: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.418: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.418: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.418: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.418: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.419: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.419: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.419: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.419: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.419: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.419: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.420: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.420: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.420: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.420: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.421: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.421: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.421: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.421: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.421: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.421: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.422: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.422: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.422: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.422: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.422: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.422: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.423: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.423: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.423: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.423: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.423: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.423: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.423: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.423: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.424: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.424: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.424: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.424: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.424: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.425: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.425: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.425: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.425: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.425: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.426: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.426: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.426: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.426: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.426: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.426: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.427: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.427: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.428: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.428: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.428: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.428: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.428: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.428: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.428: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.428: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.429: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.429: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.429: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.429: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.429: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.429: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.430: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.430: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.430: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.430: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.431: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.431: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.431: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.431: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.431: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.431: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.432: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.432: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.433: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.433: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.433: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.433: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.433: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.433: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.434: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.434: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.434: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.434: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.434: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.434: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.434: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.434: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.435: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.435: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.435: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.435: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.435: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.436: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.436: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.436: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.436: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.436: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.437: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.437: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.437: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.437: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.437: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.437: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.438: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.438: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.439: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.439: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.439: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.439: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.439: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.439: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.440: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.440: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.440: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.440: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.440: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.440: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.441: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.441: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.441: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.441: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.442: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.442: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.442: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.443: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.443: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.443: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.443: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.443: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.444: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.444: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.444: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.444: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.444: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.444: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.445: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.445: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.446: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.446: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.446: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.446: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.447: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.447: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.447: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.447: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.447: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.447: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.448: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.448: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.449: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.449: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.449: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.449: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.450: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.450: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.450: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.450: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.450: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.450: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.450: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.450: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.451: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.451: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.452: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.452: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.452: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.452: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.452: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.452: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.453: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.453: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.453: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.453: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.454: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.454: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.454: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.454: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.454: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.454: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.455: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.455: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.455: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.455: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.456: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.456: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.456: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.456: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.456: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.456: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.457: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.457: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.457: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.457: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.457: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.457: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.458: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.458: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.458: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.458: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.458: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.458: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.459: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.459: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.459: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.459: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.460: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.460: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.460: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.460: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.460: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.460: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.460: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.460: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.461: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.461: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.462: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.462: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.462: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.462: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.462: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.462: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.462: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.462: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.463: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.463: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.463: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.463: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.463: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.463: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.463: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.463: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.464: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.464: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.464: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.465: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.465: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.465: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.465: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.465: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.466: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.466: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.466: [vfs7552] CAPTURE_NUM_STATES entering state 4 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.466: Cleaning image 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.467: variance_after = 17 319s 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.467: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.467: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.467: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.467: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.467: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.468: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.468: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.468: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.468: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.468: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.468: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.469: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.469: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.469: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.469: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.469: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.470: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.470: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.470: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.470: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.470: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.471: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.471: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.471: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.471: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.471: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.471: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.472: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.472: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.473: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.473: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.473: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.473: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.473: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.473: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.474: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.474: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.474: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.474: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.475: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.475: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.476: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.476: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.476: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.476: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.477: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.477: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.478: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.478: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.478: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.478: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.478: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.478: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.479: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.479: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.479: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.480: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.480: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.480: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.480: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.480: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.481: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.481: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.481: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.481: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.482: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.482: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.483: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.483: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.483: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.483: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.483: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.483: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.484: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.484: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.484: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.484: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.484: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.484: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.484: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.484: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.485: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.485: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.485: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.485: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.486: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.486: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.486: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.486: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.486: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.486: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.487: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.487: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.487: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.487: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.487: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.487: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.488: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.488: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.488: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.488: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.488: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.488: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.489: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.489: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.490: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.490: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.490: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.490: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.490: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.490: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.491: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.491: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.491: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.491: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.491: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.492: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.492: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.492: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.492: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.492: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.493: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.493: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.493: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.493: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.493: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.493: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.494: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.494: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.495: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.495: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.495: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.495: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.495: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.495: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.496: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.496: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.496: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.496: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.496: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.496: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.496: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.497: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.497: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.497: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.497: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.497: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.498: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.498: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.498: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.498: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.498: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.498: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.498: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.498: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.499: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.499: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.499: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.500: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.500: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.500: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.500: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.500: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.501: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.501: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.501: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.501: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.501: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.501: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.502: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.502: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.502: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.502: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.502: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.502: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.503: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.503: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.503: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.503: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.503: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.503: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.504: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.504: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.504: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.504: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.504: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.504: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.505: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.505: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.506: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.506: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.506: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.506: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.506: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.506: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.507: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.507: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.507: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.507: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.507: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.507: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.507: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.507: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.508: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.508: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.508: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.508: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.508: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.509: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.509: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.509: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.509: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.509: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.510: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.510: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.510: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.510: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.510: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.510: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.511: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.511: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.512: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.512: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.512: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.512: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.512: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.512: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.512: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.512: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.513: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.513: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.513: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.513: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.513: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.513: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.514: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.514: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.514: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.514: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.514: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.515: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.515: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.515: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.515: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.515: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.516: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.516: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.516: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.516: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.516: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.516: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.516: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.516: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.517: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.517: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.517: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.517: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.517: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.517: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.518: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.518: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.518: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.519: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.519: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.519: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.519: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.519: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.520: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.520: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.520: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.520: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.520: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.520: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.520: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.520: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.521: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.521: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.521: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.521: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.521: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.522: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.522: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.522: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.522: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.522: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.523: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.523: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.523: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.523: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.523: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.523: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.524: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.524: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.524: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.524: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.524: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.524: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.525: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.525: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.526: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.526: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.526: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.526: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.526: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.526: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.526: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.526: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.527: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.527: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.527: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.527: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.527: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.527: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.528: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.528: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.528: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.528: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.528: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.528: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.528: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.529: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.529: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.529: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.529: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.530: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.530: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.530: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.530: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.531: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.531: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.531: [vfs7552] CAPTURE_NUM_STATES entering state 4 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.531: Cleaning image 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.531: variance_after = 17 319s 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.531: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.531: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.532: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.532: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.533: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.533: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.533: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.533: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.533: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.533: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.533: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.533: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.534: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.534: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.534: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.534: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.534: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.534: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.535: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.535: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.536: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.536: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.536: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.536: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.536: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.536: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.536: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.537: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.537: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.537: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.537: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.538: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.538: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.538: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.539: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.539: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.539: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.539: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.539: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.540: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.540: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.540: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.540: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.540: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.540: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.541: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.541: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.541: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.541: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.541: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.541: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.541: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.541: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.542: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.542: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.542: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.542: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.542: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.542: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.543: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.543: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.543: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.543: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.543: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.543: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.544: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.544: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.544: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.544: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.544: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.544: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.545: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.545: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.546: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.546: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.546: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.546: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.546: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.546: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.547: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.547: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.547: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.547: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.547: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.547: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.548: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.548: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.548: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.548: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.549: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.549: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.549: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.549: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.549: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.549: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.549: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.549: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.550: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.550: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.550: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.550: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.550: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.550: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.551: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.551: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.551: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.551: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.551: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.551: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.552: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.552: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.552: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.553: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.553: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.553: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.553: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.553: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.554: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.554: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.554: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.554: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.554: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.554: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.555: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.555: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.555: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.555: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.555: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.555: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.555: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.555: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.556: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.556: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.556: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.556: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.556: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.556: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.557: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.557: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.557: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.557: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.557: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.558: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.558: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.558: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.558: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.558: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.558: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.559: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.559: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.559: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.559: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.559: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.559: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.560: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.560: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.560: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.560: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.560: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.560: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.560: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.560: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.561: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.561: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.562: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.562: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.562: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.562: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.562: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.562: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.563: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.563: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.563: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.563: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.563: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.563: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.564: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.564: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.564: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.564: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.564: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.564: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.565: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.565: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.565: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.565: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.565: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.565: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.565: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.566: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.566: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.566: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.566: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.566: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.567: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.567: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.567: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.567: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.567: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.567: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.568: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.568: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.569: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.569: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.569: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.569: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.569: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.569: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.570: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.570: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.570: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.570: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.570: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.570: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.570: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.570: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.571: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.571: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.571: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.571: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.572: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.572: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.572: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.572: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.572: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.572: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.573: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.573: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.573: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.573: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.573: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.573: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.574: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.574: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.575: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.575: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.575: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.575: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.575: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.575: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.575: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.575: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.576: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.576: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.576: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.576: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.577: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.577: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.577: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.577: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.577: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.577: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.578: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.578: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.578: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.578: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.578: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.578: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.579: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.579: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.580: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.580: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.580: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.580: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.580: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.580: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.581: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.581: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.581: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.581: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.581: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.581: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.582: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.582: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.582: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.582: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.583: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.583: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.583: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.583: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.583: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.583: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.584: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.584: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.584: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.585: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.585: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.585: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.585: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.585: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.586: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.586: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.586: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.586: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.586: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.586: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.586: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.586: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.587: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.587: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.587: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.587: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.587: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.588: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.588: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.588: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.588: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.588: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.589: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.589: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.590: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.590: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.590: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.590: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.590: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.591: [vfs7552] CAPTURE_NUM_STATES entering state 4 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.591: Cleaning image 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.591: variance_after = 17 319s 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.591: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.591: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.591: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.592: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.592: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.592: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.592: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.592: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.592: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.592: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.593: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.593: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.593: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.594: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.594: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.594: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.594: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.594: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.595: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.595: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.595: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.595: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.595: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.595: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.596: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.596: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.596: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.596: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.596: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.596: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.597: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.597: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.597: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.597: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.597: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.597: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.598: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.598: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.598: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.598: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.598: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.598: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.599: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.599: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.599: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.600: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.600: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.600: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.600: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.600: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.601: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.601: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.601: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.601: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.601: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.601: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.602: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.602: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.602: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.602: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.603: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.603: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.603: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.603: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.603: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.603: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.604: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.604: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.604: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.605: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.605: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.605: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.605: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.605: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.606: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.606: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.606: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.606: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.606: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.606: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.607: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.607: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.607: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.607: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.607: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.607: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.607: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.607: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.608: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.608: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.608: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.608: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.608: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.608: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.609: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.609: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.609: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.609: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.609: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.610: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.610: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.610: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.610: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.610: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.610: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.610: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.611: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.611: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.611: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.611: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.611: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.611: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.612: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.612: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.612: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.613: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.613: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.613: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.613: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.613: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.614: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.614: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.614: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.614: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.614: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.614: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.614: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.614: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.615: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.615: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.615: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.615: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.616: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.616: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.616: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.616: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.616: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.616: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.617: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.617: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.617: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.617: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.617: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.617: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.617: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.617: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.618: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.618: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.618: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.618: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.618: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.618: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.619: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.619: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.619: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.620: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.620: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.620: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.620: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.620: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.620: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.620: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.621: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.621: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.621: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.621: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.621: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.621: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.622: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.622: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.622: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.622: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.623: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.623: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.623: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.623: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.623: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.623: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.623: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.623: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.624: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.624: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.625: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.625: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.625: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.625: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.625: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.625: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.626: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.626: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.626: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.626: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.626: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.626: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.627: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.627: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.627: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.627: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.627: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.627: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.627: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.627: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.628: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.628: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.628: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.628: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.629: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.629: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.629: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.629: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.629: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.629: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.630: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.630: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.630: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.631: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.631: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.631: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.631: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.631: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.632: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.632: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.632: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.632: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.632: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.632: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.633: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.633: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.633: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.633: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.634: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.634: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.634: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.634: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.634: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.634: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.634: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.634: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.635: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.635: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.635: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.635: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.635: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.635: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.636: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.636: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.637: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.637: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.637: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.637: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.637: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.637: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.638: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.638: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.638: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.638: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.638: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.638: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.638: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.638: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.639: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.639: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.639: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.639: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.639: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.639: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.640: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.640: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.640: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.640: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.640: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.641: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.641: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.641: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.641: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.641: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.642: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.642: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.643: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.643: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.643: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.643: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.643: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.644: [vfs7552] CAPTURE_NUM_STATES entering state 4 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.644: Cleaning image 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.644: variance_after = 17 319s 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.644: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.644: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.645: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.645: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.646: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.646: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.646: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.646: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.646: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.646: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.647: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.647: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.647: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.647: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.647: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.647: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.648: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.648: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.648: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.648: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.649: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.649: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.649: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.649: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.649: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.649: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.650: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.650: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.650: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.650: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.650: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.650: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.650: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.650: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.651: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.651: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.651: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.651: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.651: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.651: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.652: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.652: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.652: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.652: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.653: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.653: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.653: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.653: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.654: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.654: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.654: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.654: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.654: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.654: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.655: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.655: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.655: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.655: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.655: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.655: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.656: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.656: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.656: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.656: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.656: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.656: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.656: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.656: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.657: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.657: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.657: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.657: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.657: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.657: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.658: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.658: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.658: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.658: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.658: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.659: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.659: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.659: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.659: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.659: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.660: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.660: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.660: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.660: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.660: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.660: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.661: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.661: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.661: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.661: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.661: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.662: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.662: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.662: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.662: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.663: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.663: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.663: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.663: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.663: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.663: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.664: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.664: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.664: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.664: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.664: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.664: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.665: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.665: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.665: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.665: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.665: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.665: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.665: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.665: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.666: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.666: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.666: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.666: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.666: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.666: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.667: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.667: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.667: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.667: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.667: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.668: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.668: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.668: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.668: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.668: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.669: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.669: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.669: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.669: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.669: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.669: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.670: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.670: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.671: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.671: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.671: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.671: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.671: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.671: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.671: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.671: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.672: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.672: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.672: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.672: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.673: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.673: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.673: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.673: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.673: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.673: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.674: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.674: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.675: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.675: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.675: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.675: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.675: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.675: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.676: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.676: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.676: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.676: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.676: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.676: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.677: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.677: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.677: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.677: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.677: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.677: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.678: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.678: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.679: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.679: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.679: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.679: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.679: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.679: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.680: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.680: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.680: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.680: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.680: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.680: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.681: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.681: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.681: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.681: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.681: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.681: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.681: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.682: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.682: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.682: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.682: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.682: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.683: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.683: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.683: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.683: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.683: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.683: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.684: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.684: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.685: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.685: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.685: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.685: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.685: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.685: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.686: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.686: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.686: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.686: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.686: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.686: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.687: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.687: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.687: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.687: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.687: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.687: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.688: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.688: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.688: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.688: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.688: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.688: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.689: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.689: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.690: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.690: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.690: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.690: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.691: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.691: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.692: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.692: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.692: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.692: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.693: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.693: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.693: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.694: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.694: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.694: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.694: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.694: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.694: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.695: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.695: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.695: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.695: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.695: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.696: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.696: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.697: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.697: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.697: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.697: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.698: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.698: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.698: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.698: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.698: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.699: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.699: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.699: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.700: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.700: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.700: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.700: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.700: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.701: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.701: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.701: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.701: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.701: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.701: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.701: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.702: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.702: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.702: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.702: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.702: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.703: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.703: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.704: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.704: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.704: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.704: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.704: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.705: [vfs7552] CAPTURE_NUM_STATES entering state 4 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.705: Cleaning image 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.705: variance_after = 16 319s 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.705: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.705: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.705: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.706: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.706: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.706: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.706: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.706: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.706: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.706: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.707: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.707: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.708: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.708: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.708: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.708: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.708: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.708: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.709: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.709: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.709: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.709: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.710: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.710: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.710: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.710: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.710: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.710: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.710: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.710: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.711: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.711: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.711: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.711: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.711: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.711: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.712: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.712: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.713: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.713: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.713: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.713: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.713: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.713: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.713: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.713: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.714: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.714: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.714: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.714: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.715: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.715: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.715: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.715: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.715: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.715: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.716: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.716: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.717: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.717: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.717: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.717: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.717: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.717: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.717: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.718: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.718: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.718: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.718: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.718: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.718: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.718: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.718: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.719: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.719: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.719: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.719: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.719: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.719: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.720: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.720: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.720: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.720: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.720: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.720: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.720: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.720: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.721: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.721: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.722: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.722: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.722: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.722: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.722: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.722: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.722: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.722: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.723: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.723: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.723: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.723: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.724: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.724: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.724: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.724: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.724: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.724: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.725: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.725: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.725: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.725: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.725: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.725: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.726: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.726: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.726: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.727: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.727: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.727: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.727: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.727: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.727: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.727: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.728: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.728: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.728: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.728: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.728: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.728: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.729: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.729: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.729: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.729: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.729: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.729: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.730: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.730: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.730: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.730: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.730: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.730: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.731: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.731: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.731: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.731: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.731: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.731: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.732: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.732: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.732: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.732: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.732: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.732: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.733: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.733: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.733: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.733: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.733: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.733: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.733: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.734: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.734: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.734: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.734: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.734: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.734: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.734: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.735: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.735: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.735: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.735: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.735: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.735: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.736: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.736: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.736: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.736: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.737: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.737: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.737: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.737: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.737: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.737: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.737: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.737: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.738: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.738: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.738: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.738: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.738: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.738: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.739: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.739: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.739: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.739: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.739: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.739: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.740: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.740: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.740: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.740: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.740: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.740: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.741: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.741: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.742: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.742: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.742: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.742: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.742: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.742: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.743: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.743: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.743: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.743: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.743: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.743: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.743: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.743: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.744: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.744: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.744: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.744: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.745: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.745: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.745: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.745: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.745: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.745: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.746: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.746: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.746: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.746: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.746: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.746: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.747: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.747: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.748: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.748: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.748: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.748: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.748: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.748: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.749: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.749: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.749: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.749: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.749: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.749: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.749: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.749: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.750: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.750: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.750: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.750: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.750: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.751: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.751: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.751: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.751: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.751: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.752: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.752: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.752: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.752: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.752: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.752: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.753: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.753: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.754: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.754: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.754: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.754: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.754: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.754: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.755: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.755: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.755: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.755: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.755: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.755: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.756: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.756: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.756: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.756: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.757: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.757: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.757: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.757: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.757: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.757: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.757: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.758: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.758: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.758: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.758: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.758: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.759: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.759: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.760: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.760: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.760: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.760: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.760: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.761: [vfs7552] CAPTURE_NUM_STATES entering state 4 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.761: Cleaning image 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.761: variance_after = 17 319s 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.761: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.761: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.762: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.762: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.762: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.762: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.762: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.762: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.763: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.763: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.763: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.763: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.763: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.763: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.764: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.764: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.765: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.765: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.765: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.765: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.765: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.765: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.765: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.765: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.766: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.766: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.766: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.766: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.766: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.767: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.767: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.767: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.767: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.767: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.768: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.768: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.768: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.768: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.768: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.768: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.769: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.769: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.770: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.770: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.770: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.770: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.770: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.770: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.770: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.770: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.771: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.771: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.771: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.771: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.771: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.771: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.772: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.772: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.772: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.772: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.773: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.773: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.773: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.773: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.773: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.773: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.774: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.774: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.775: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.775: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.775: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.775: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.775: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.775: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.775: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.775: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.776: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.776: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.776: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.776: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.777: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.777: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.777: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.777: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.777: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.777: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.778: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.778: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.778: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.778: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.778: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.778: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.779: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.779: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.779: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.779: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.779: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.779: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.780: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.780: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.781: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.781: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.781: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.781: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.781: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.781: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.782: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.782: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.782: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.782: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.782: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.782: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.783: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.783: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.783: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.783: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.783: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.783: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.784: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.784: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.784: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.784: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.784: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.784: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.784: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.784: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.785: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.785: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.785: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.785: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.785: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.785: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.786: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.786: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.786: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.786: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.787: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.787: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.787: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.787: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.787: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.787: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.787: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.787: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.788: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.788: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.788: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.788: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.788: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.788: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.789: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.789: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.789: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.789: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.789: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.789: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.790: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.790: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.791: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.791: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.791: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.791: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.791: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.791: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.791: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.791: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.792: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.792: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.792: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.792: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.792: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.792: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.793: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.793: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.793: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.793: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.793: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.793: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.794: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.794: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.794: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.794: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.794: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.794: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.795: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.795: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.795: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.795: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.795: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.795: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.795: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.795: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.796: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.796: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.796: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.796: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.796: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.796: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.797: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.797: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.797: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.797: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.798: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.798: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.798: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.798: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.798: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.798: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.799: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.799: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.799: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.799: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.799: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.799: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.799: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.799: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.800: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.800: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.800: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.800: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.800: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.800: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.801: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.801: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.802: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.802: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.802: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.802: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.802: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.802: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.802: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.803: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.803: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.803: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.803: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.803: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.803: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.803: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.803: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.804: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.804: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.804: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.804: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.804: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.804: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.804: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.804: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.805: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.805: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.805: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.805: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.805: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.805: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.805: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.806: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.806: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.806: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.806: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.806: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.806: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.806: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.807: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.807: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.808: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.808: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.808: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.808: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.808: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.808: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.809: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.809: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.809: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.809: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.809: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.809: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.809: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.810: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.810: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.810: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.811: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.811: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.811: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.811: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.811: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.812: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.812: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.813: [vfs7552] CAPTURE_NUM_STATES entering state 4 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.813: Cleaning image 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.813: variance_after = 16 319s 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.813: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.813: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.813: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.813: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.814: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.814: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.814: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.814: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.814: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.814: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.815: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.815: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.815: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.815: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.815: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.815: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.816: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.816: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.816: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.816: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.816: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.816: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.817: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.817: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.817: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.818: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.818: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.818: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.818: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.818: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.818: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.818: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.819: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.819: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.819: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.819: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.819: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.819: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.820: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.820: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.820: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.820: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.820: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.820: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.821: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.821: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.821: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.821: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.821: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.821: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.822: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.822: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.822: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.822: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.822: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.822: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.823: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.823: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.823: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.823: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.823: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.823: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.824: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.824: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.824: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.824: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.824: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.824: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.825: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.825: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.826: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.826: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.826: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.826: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.826: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.826: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.827: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.827: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.827: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.827: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.827: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.827: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.828: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.828: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.828: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.828: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.828: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.829: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.829: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.829: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.829: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.829: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.829: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.830: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.830: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.830: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.830: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.830: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.830: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.831: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.831: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.831: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.831: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.831: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.831: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.831: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.832: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.832: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.832: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.832: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.832: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.832: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.833: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.833: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.833: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.833: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.833: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.833: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.834: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.834: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.834: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.834: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.834: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.834: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.835: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.835: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.836: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.836: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.836: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.836: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.836: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.836: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.837: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.837: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.837: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.837: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.837: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.837: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.838: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.838: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.838: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.838: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.839: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.839: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.839: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.839: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.840: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.840: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.840: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.840: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.841: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.841: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.841: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.841: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.841: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.841: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.841: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.841: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.842: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.842: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.842: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.843: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.843: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.843: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.843: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.843: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.844: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.844: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.844: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.844: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.844: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.844: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.845: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.845: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.845: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.845: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.845: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.845: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.846: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.846: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.846: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.846: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.847: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.847: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.847: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.847: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.847: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.847: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.848: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.848: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.848: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.849: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.849: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.849: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.849: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.849: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.850: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.850: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.850: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.850: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.850: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.851: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.851: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.851: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.851: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.851: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.852: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.852: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.852: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.852: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.853: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.853: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.853: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.853: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.853: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.853: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.854: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.854: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.854: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.854: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.854: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.854: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.855: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.855: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.855: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.855: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.855: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.856: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.856: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.856: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.856: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.856: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.856: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.856: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.856: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.857: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.857: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.858: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.858: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.858: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.858: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.858: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.858: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.858: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.858: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.859: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.859: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.859: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.859: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.859: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.859: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.859: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.860: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.860: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.860: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.860: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.860: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.860: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.861: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.861: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.861: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.861: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.862: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.862: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.862: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.862: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.862: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.862: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.862: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.862: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.863: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.863: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.863: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.864: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.864: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.864: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.864: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.865: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.865: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.865: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.865: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.865: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.866: [vfs7552] CAPTURE_NUM_STATES entering state 4 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.866: Cleaning image 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.866: variance_after = 2168 319s 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.866: [vfs7552] CAPTURE_NUM_STATES completed successfully 319s (process:2572): libfprint-device-DEBUG: 05:02:18.866: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 319s (process:2572): libfprint-image_device-DEBUG: 05:02:18.866: Image device reported finger status: on 319s (process:2572): libfprint-image_device-DEBUG: 05:02:18.866: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.916: changing to 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.916: [vfs7552] QUERY DATA READY entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.916: Sending vfs7552_is_image_ready 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.917: [vfs7552] QUERY DATA READY entering state 1 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.917: Receiving 64 bytes 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.917: Got 6 bytes out of 64 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.917: [vfs7552] QUERY DATA READY completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.917: [vfs7552] CAPTURE_NUM_STATES entering state 1 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.917: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.917: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.917: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.918: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.918: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.919: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.919: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.919: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.919: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.919: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.920: [vfs7552] CAPTURE_NUM_STATES entering state 2 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.920: [vfs7552] REQUEST CHUNK entering state 0 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.920: Sending vfs7552_read_image_chunk 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.920: [vfs7552] REQUEST CHUNK completed successfully 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.921: [vfs7552] CAPTURE_NUM_STATES entering state 3 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.921: [vfs7552] CAPTURE_NUM_STATES entering state 4 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.921: Cleaning image 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.921: variance_after = 2082 319s 319s (process:2572): libfprint-SSM-DEBUG: 05:02:18.921: [vfs7552] CAPTURE_NUM_STATES completed successfully 319s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.921: Image captured 319s (process:2572): libfprint-image_device-DEBUG: 05:02:18.921: Image device captured an image 319s (process:2572): libfprint-image_device-DEBUG: 05:02:18.922: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 319s (process:2572): libfprint-device-DEBUG: 05:02:18.922: Device reported finger status change: FP_FINGER_STATUS_PRESENT 319s (process:2572): libfprint-image-DEBUG: 05:02:18.946: Minutiae scan completed in 0.024198 secs 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.971: changing to 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.971: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.971: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.972: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.972: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.973: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.973: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.973: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.973: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.973: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.973: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.973: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.974: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.974: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.974: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.974: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.975: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.975: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.975: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.975: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.976: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.976: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.976: [vfs7552] CAPTURE_NUM_STATES entering state 4 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.976: Cleaning image 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.977: variance_after = 2003 320s 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.977: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.977: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.977: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.977: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.978: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.978: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.978: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.978: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.978: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.978: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.979: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.979: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.979: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.979: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.979: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.980: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.980: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.980: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.980: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.980: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.981: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.981: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.981: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.981: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.981: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.981: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.982: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.982: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.982: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.982: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.982: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.983: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.983: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.983: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.984: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.984: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.984: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.984: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.984: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.984: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.985: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.985: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.985: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.985: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.985: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.985: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.986: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.986: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.986: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.986: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.987: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.987: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.987: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.987: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.987: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.987: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.988: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.988: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.988: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.988: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.988: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.988: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.989: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.989: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.990: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.990: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.990: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.990: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.990: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.990: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.991: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.991: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.991: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.991: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.991: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.991: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.992: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.992: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.992: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.992: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.992: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.993: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.993: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.993: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.993: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.993: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.993: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.993: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.994: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.994: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.994: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.994: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.994: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.994: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.995: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.995: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.995: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.995: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.995: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.995: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.996: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.996: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.997: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.997: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.997: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.997: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.997: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.997: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.998: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.998: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.998: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.998: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.998: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.998: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.998: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.998: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.999: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.999: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:18.999: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:18.999: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.000: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.000: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.000: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.000: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.000: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.000: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.001: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.001: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.001: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.001: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.001: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.001: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.002: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.002: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.003: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.003: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.003: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.003: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.003: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.003: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.004: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.004: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.004: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.004: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.004: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.004: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.005: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.005: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.005: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.005: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.005: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.006: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.006: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.006: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.006: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.006: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.006: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.006: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.007: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.007: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.007: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.007: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.007: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.007: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.008: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.008: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.008: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.008: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.008: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.008: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.009: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.009: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.009: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.010: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.010: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.010: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.010: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.010: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.011: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.011: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.011: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.011: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.011: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.011: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.011: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.011: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.012: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.012: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.012: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.012: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.012: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.012: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.013: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.013: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.013: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.013: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.013: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.013: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.014: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.014: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.014: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.014: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.014: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.015: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.015: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.015: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.015: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.015: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.015: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.016: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.016: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.016: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.016: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.016: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.016: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.016: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.016: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.017: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.017: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.017: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.017: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.018: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.018: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.018: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.018: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.018: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.018: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.018: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.019: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.019: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.019: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.019: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.019: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.019: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.019: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.020: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.020: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.020: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.020: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.020: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.020: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.020: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.020: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.021: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.021: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.021: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.021: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.021: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.021: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.021: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.022: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.022: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.022: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.022: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.022: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.022: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.022: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.022: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.022: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.023: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.023: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.023: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.023: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.023: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.023: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.024: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.024: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.024: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.024: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.024: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.024: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.024: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.024: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.025: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.025: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.025: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.025: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.025: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.025: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.025: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.025: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.026: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.026: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.026: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.026: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.026: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.026: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.026: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.026: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.027: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.027: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.027: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.028: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.028: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.028: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.028: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.028: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.028: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.028: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.029: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.029: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.029: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.029: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.029: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.029: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.029: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.029: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.030: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.030: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.030: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.030: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.030: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.030: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.030: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.030: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.031: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.031: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.031: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.031: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.031: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.031: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.031: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.032: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.032: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.032: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.032: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.032: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.032: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.032: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.033: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.033: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.033: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.033: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.033: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.033: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.033: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.033: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.034: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.034: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.034: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.034: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.034: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.034: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.034: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.034: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.035: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.035: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.035: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.036: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.036: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.036: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.036: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.036: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.036: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.036: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.037: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.037: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.037: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.037: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.037: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.037: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.037: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.037: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.038: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.038: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.038: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.038: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.038: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.038: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.038: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.039: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.039: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.039: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.039: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.039: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.039: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.039: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.040: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.040: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.040: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.040: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.040: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.040: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.040: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.040: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.041: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.041: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.042: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.042: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.042: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.042: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.042: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.042: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.042: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.042: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.043: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.043: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.043: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.043: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.043: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.043: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.043: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.043: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.044: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.044: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.044: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.044: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.044: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.044: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.045: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.045: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.045: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.045: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.045: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.045: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.045: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.045: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.046: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.046: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.047: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.047: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.047: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.047: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.047: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.047: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.047: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.047: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.048: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.048: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.048: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.048: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.048: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.048: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.048: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.049: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.049: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.049: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.049: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.049: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.049: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.049: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.050: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.050: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.050: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.050: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.050: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.050: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.050: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.050: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.051: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.051: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.052: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.052: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.052: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.052: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.052: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.052: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.052: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.052: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.053: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.053: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.053: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.053: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.053: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.053: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.054: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.054: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.054: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.054: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.054: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.054: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.054: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.054: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.055: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.055: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.056: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.056: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.056: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.056: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.056: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.056: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.056: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.056: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.057: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.057: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.057: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.057: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.057: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.057: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.057: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.058: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.058: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.058: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.058: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.058: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.058: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.058: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.059: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.059: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.059: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.059: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.059: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.059: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.059: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.059: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.060: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.060: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.061: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.061: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.061: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.061: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.061: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.061: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.061: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.061: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.062: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.062: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.062: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.062: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.062: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.062: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.062: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.063: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.063: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.063: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.063: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.063: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.063: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.063: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.064: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.064: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.064: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.064: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.064: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.064: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.064: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.064: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.065: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.065: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.066: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.066: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.066: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.066: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.066: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.066: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.066: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.066: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.067: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.067: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.067: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.067: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.067: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.067: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.067: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.067: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.068: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.068: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.068: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.068: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.068: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.068: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.069: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.069: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.069: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.069: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.069: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.069: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.069: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.069: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.070: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.070: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.070: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.070: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.070: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.070: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.070: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.070: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.071: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.071: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.071: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.071: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.071: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.071: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.071: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.072: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.072: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.072: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.073: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.073: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.073: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.073: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.073: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.073: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.073: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.073: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.074: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.074: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.074: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.074: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.074: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.074: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.075: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.075: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.075: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.075: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.075: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.075: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.075: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.075: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.076: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.076: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.076: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.077: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.077: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.077: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.077: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.077: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.077: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.077: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.078: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.078: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.078: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.078: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.078: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.078: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.078: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.078: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.079: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.079: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.079: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.079: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.079: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.079: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.080: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.080: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.080: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.080: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.080: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.080: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.080: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.080: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.081: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.081: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.081: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.081: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.081: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.081: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.081: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.081: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.082: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.082: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.082: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.083: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.083: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.083: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.083: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.083: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.083: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.083: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.084: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.084: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.084: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.084: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.084: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.084: Sending vfs7552_is_image_ready 320s Executing: libfprint-2/driver-vfs7552.test 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.085: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.085: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.086: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.086: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.086: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.086: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.086: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.086: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.086: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.086: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.087: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.087: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.087: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.087: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.087: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.087: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.087: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.087: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.088: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.088: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.088: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.088: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.088: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.088: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.089: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.089: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.089: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.089: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.089: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.089: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.089: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.089: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.090: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.090: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.090: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.091: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.091: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.091: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.091: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.091: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.091: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.091: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.092: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.092: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.092: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.092: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.092: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.092: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.092: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.092: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.093: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.093: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.093: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.093: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.093: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.093: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.094: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.094: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.094: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.094: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.094: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.094: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.094: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.094: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.095: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.095: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.095: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.095: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.095: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.095: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.095: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.095: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.096: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.096: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.097: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.097: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.097: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.097: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.097: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.097: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.097: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.097: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.098: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.098: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.098: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.098: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.098: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.098: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.098: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.098: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.099: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.099: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.099: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.099: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.099: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.099: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.100: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.100: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.100: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.100: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.100: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.100: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.100: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.100: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.101: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.101: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.101: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.102: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.102: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.102: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.102: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.102: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.102: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.102: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.103: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.103: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.103: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.103: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.103: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.103: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.103: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.103: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.104: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.104: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.104: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.104: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.104: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.104: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.104: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.105: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.105: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.105: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.105: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.105: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.105: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.105: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.106: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.106: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.106: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.106: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.106: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.106: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.106: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.106: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.107: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.107: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.107: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.108: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.108: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.108: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.108: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.108: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.108: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.108: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.109: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.109: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.109: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.109: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.109: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.109: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.109: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.109: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.110: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.110: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.110: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.110: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.110: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.110: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.111: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.111: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.111: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.111: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.111: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.111: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.111: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.111: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.112: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.112: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.112: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.112: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.112: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.112: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.112: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.112: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.113: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.113: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.114: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.114: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.114: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.114: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.114: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.114: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.114: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.114: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.115: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.115: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.115: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.115: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.115: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.115: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.116: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.116: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.116: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.116: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.116: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.116: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.116: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.116: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.117: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.117: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.118: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.118: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.118: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.118: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.118: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.118: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.118: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.118: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.119: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.119: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.119: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.119: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.119: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.119: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.120: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.120: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.120: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.120: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.120: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.120: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.120: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.120: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.121: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.121: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.122: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.122: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.122: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.122: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.122: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.122: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.122: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.122: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.123: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.123: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.123: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.123: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.123: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.123: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.124: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.124: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.124: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.124: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.124: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.124: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.124: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.124: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.125: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.125: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.125: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.125: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.125: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.125: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.125: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.125: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.126: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.126: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.126: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.127: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.127: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.127: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.127: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.127: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.127: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.127: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.128: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.128: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.128: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.128: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.128: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.128: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.128: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.128: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.129: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.129: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.129: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.129: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.129: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.129: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.130: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.130: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.130: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.130: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.130: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.130: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.130: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.130: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.131: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.131: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.131: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.132: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.132: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.132: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.132: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.132: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.132: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.132: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.133: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.133: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.133: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.133: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.133: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.133: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.133: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.133: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.134: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.134: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.134: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.134: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.134: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.134: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.134: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.134: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.135: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.135: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.135: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.135: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.135: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.135: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.136: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.136: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.136: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.137: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.137: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.137: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.137: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.137: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.137: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.137: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.138: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.138: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.138: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.138: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.138: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.138: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.138: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.138: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.139: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.139: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.139: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.139: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.139: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.139: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.140: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.140: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.140: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.140: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.140: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.140: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.140: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.140: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.141: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.141: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.141: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.141: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.141: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.141: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.141: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.141: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.142: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.142: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.142: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.143: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.143: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.143: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.143: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.143: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.143: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.143: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.144: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.144: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.144: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.144: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.144: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.144: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.144: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.144: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.145: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.145: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.145: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.145: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.145: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.145: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.145: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.145: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.146: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.146: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.146: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.146: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.146: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.146: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.146: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.147: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.147: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.147: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.147: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.147: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.147: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.147: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.148: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.148: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.148: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.148: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.148: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.148: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.148: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.148: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.149: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.149: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.149: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.149: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.149: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.149: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.149: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.149: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.150: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.150: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.150: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.151: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.151: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.151: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.151: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.151: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.151: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.151: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.152: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.152: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.152: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.152: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.152: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.152: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.152: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.152: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.153: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.153: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.153: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.153: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.153: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.153: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.153: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.153: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.154: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.154: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.154: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.154: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.154: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.154: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.154: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.155: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.155: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.155: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.155: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.155: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.155: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.155: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.156: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.156: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.156: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.156: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.156: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.156: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.156: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.156: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.157: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.157: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.157: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.157: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.157: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.157: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.157: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.157: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.158: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.158: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.159: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.159: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.159: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.159: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.159: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.159: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.159: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.159: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.160: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.160: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.160: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.160: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.160: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.160: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.160: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.160: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.161: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.161: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.161: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.161: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.161: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.161: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.161: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.161: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.162: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.162: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.162: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.162: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.162: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.162: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.162: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.162: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.163: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.163: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.163: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.163: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.163: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.163: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.163: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.164: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.164: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.164: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.164: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.164: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.164: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.164: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.165: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.165: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.165: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.165: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.165: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.165: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.165: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.165: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.166: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.166: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.166: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.166: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.166: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.167: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.167: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.168: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.168: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.168: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.168: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.168: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.169: [vfs7552] CAPTURE_NUM_STATES entering state 4 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.169: Cleaning image 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.169: variance_after = 1737 320s 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.169: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.169: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.169: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.169: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.169: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.170: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.170: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.170: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.170: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.170: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.170: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.170: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.171: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.171: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.171: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.171: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.171: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.171: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.171: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.172: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.172: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.172: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.172: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.172: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.172: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.172: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.172: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.173: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.173: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.173: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.173: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.173: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.173: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.173: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.173: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.174: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.174: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.174: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.174: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.174: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.174: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.174: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.174: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.175: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.175: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.176: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.176: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.176: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.176: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.176: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.176: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.176: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.176: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.177: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.177: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.177: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.177: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.177: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.177: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.177: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.177: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.178: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.178: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.178: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.178: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.178: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.178: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.178: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.179: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.179: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.179: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.179: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.179: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.179: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.179: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.180: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.180: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.180: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.180: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.180: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.180: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.180: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.180: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.181: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.181: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.181: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.182: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.182: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.182: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.182: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.182: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.182: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.182: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.183: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.183: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.183: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.183: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.183: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.183: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.183: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.183: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.184: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.184: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.184: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.184: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.184: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.184: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.184: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.184: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.185: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.185: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.185: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.185: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.185: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.185: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.186: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.186: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.186: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.186: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.186: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.186: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.186: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.186: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.187: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.187: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.187: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.187: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.187: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.187: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.187: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.187: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.188: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.188: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.188: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.188: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.188: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.188: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.188: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.188: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.189: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.189: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.190: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.190: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.190: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.190: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.190: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.190: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.190: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.190: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.191: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.191: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.191: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.191: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.191: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.191: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.191: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.192: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.192: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.192: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.192: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.192: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.192: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.192: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.193: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.193: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.193: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.193: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.193: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.193: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.193: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.193: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.194: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.194: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.195: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.195: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.195: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.195: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.195: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.195: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.195: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.195: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.196: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.196: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.196: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.196: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.196: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.196: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.196: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.196: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.197: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.197: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.197: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.197: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.197: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.197: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.198: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.198: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.198: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.198: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.198: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.198: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.198: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.198: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.199: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.199: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.199: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.199: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.199: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.199: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.199: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.199: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.200: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.200: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.200: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.200: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.200: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.201: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.201: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.201: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.201: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.201: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.201: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.201: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.202: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.202: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.202: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.202: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.202: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.202: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.203: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.203: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.203: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.203: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.203: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.203: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.203: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.203: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.204: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.204: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.204: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.204: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.204: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.204: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.204: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.204: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.205: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.205: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.205: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.205: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.205: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.205: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.205: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.205: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.206: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.206: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.206: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.206: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.206: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.206: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.206: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.206: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.207: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.207: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.207: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.207: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.207: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.207: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.208: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.208: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.208: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.208: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.208: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.208: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.208: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.208: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.209: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.209: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.209: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.209: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.209: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.209: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.209: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.209: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.210: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.210: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.210: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.210: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.210: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.210: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.210: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.210: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.211: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.211: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.211: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.211: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.211: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.211: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.211: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.211: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.212: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.212: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.212: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.212: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.212: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.212: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.212: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.212: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.213: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.213: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.213: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.213: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.214: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.214: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.214: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.214: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.214: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.214: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.214: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.215: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.215: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.215: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.215: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.215: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.215: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.215: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.215: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.215: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.215: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.216: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.216: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.216: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.216: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.216: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.216: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.216: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.216: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.216: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.217: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.217: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.217: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.218: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.218: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.218: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.218: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.218: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.218: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.218: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.219: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.219: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.219: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.219: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.219: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.219: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.219: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.219: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.220: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.220: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.220: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.220: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.220: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.220: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.220: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.220: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.221: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.221: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.221: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.221: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.221: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.221: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.222: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.222: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.222: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.222: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.222: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.222: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.222: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.222: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.223: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.223: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.223: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.223: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.223: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.223: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.223: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.223: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.224: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.224: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.225: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.225: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.225: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.225: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.225: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.225: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.225: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.225: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.226: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.226: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.226: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.226: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.226: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.226: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.226: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.226: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.227: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.227: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.227: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.227: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.227: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.227: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.228: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.228: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.228: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.228: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.228: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.228: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.228: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.228: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.229: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.229: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.230: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.230: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.230: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.230: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.230: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.230: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.230: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.230: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.231: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.231: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.231: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.231: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.231: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.231: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.231: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.231: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.232: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.232: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.232: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.232: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.232: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.232: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.233: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.233: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.233: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.233: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.233: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.233: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.233: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.233: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.234: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.234: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.234: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.234: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.234: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.234: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.234: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.234: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.235: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.235: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.235: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.235: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.236: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.236: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.236: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.236: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.236: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.236: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.237: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.237: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.237: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.237: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.237: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.237: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.237: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.237: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.238: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.238: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.238: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.238: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.238: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.238: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.238: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.239: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.239: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.239: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.239: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.239: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.239: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.239: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.240: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.240: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.240: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.240: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.240: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.240: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.240: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.240: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.241: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.241: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.241: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.241: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.241: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.241: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.241: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.241: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.242: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.242: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.243: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.243: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.243: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.243: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.243: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.243: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.243: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.243: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.244: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.244: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.244: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.244: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.244: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.244: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.244: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.244: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.245: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.245: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.245: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.245: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.245: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.245: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.245: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.246: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.246: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.246: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.246: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.246: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.246: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.246: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.247: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.247: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.247: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.247: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.247: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.247: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.247: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.247: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.248: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.248: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.248: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.248: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.248: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.248: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.248: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.248: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.249: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.249: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.249: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.249: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.249: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.249: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.249: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.249: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.250: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.250: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.250: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.251: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.251: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.251: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.251: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.251: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.251: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.251: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.252: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.252: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.252: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.252: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.252: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.252: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.252: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.252: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.253: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.253: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.253: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.253: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.253: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.253: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.253: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.253: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.254: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.254: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.254: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.254: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.254: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.254: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.254: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.255: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.255: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.255: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.255: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.255: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.255: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.255: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.256: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.256: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.256: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.256: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.256: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.256: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.256: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.256: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.257: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.257: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.257: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.257: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.257: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.257: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.257: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.257: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.258: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.258: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.258: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.259: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.259: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.259: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.259: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.259: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.259: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.259: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.260: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.260: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.260: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.260: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.260: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.260: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.260: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.260: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.261: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.261: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.261: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.261: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.261: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.261: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.262: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.262: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.262: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.262: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.262: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.262: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.262: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.262: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.263: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.263: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.263: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.263: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.263: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.263: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.263: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.263: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.264: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.264: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.265: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.265: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.265: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.265: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.265: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.265: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.265: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.265: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.266: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.266: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.266: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.266: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.266: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.266: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.266: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.266: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.267: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.267: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.267: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.267: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.267: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.267: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.268: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.268: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.268: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.268: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.268: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.268: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.268: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.268: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.269: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.269: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.270: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.270: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.270: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.270: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.270: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.270: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.270: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.270: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.271: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.271: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.271: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.271: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.271: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.271: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.272: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.272: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.272: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.272: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.272: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.272: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.272: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.272: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.273: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.273: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.274: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.274: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.274: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.274: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.274: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.274: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.274: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.274: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.275: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.275: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.275: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.275: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.275: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.275: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.276: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.276: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.276: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.277: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.277: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.277: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.277: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.277: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.277: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.277: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.278: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.278: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.278: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.278: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.278: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.278: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.278: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.278: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.279: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.279: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.279: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.279: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.279: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.279: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.280: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.280: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.280: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.280: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.280: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.280: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.280: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.280: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.281: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.281: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.281: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.281: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.281: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.281: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.281: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.281: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.282: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.282: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.282: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.282: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.282: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.282: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.282: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.282: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.283: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.283: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.284: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.284: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.284: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.284: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.284: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.284: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.284: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.284: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.285: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.285: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.285: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.285: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.285: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.285: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.285: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.285: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.286: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.286: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.286: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.286: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.286: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.286: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.286: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.286: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.287: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.287: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.287: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.287: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.287: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.287: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.287: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.287: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.288: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.288: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.288: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.288: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.288: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.288: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.289: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.289: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.289: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.289: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.289: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.289: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.289: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.289: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.290: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.290: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.290: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.290: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.290: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.290: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.290: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.290: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.291: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.291: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.292: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.292: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.292: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.292: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.292: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.292: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.292: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.292: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.293: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.293: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.293: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.293: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.293: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.293: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.293: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.293: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.294: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.294: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.294: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.294: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.294: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.294: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.294: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.294: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.295: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.295: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.295: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.295: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.295: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.295: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.295: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.295: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.296: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.296: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.296: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.296: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.296: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.296: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.296: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.297: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.297: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.297: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.297: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.297: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.297: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.297: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.298: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.298: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.298: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.298: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.298: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.298: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.298: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.298: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.299: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.299: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.300: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.300: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.300: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.300: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.300: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.300: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.300: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.300: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.301: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.301: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.301: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.301: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.301: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.301: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.302: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.302: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.302: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.302: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.302: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.302: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.302: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.302: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.303: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.303: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.304: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.304: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.304: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.304: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.304: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.304: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.305: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.305: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.305: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.305: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.305: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.305: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.305: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.305: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.306: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.306: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.307: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.307: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.307: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.307: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.307: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.307: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.307: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.307: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.308: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.308: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.308: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.308: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.308: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.308: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.309: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.309: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.310: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.310: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.310: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.310: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.310: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.310: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.310: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.310: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.311: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.311: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.311: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.311: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.311: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.311: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.312: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.312: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.312: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.312: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.312: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.312: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.312: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.313: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.313: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.313: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.314: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.314: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.314: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.314: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.314: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.314: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.315: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.315: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.315: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.315: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.315: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.315: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.315: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.315: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.316: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.316: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.317: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.317: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.317: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.317: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.317: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.317: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.317: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.317: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.318: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.318: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.318: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.318: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.318: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.318: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.319: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.319: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.320: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.320: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.320: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.320: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.320: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.320: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.320: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.320: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.321: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.321: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.321: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.321: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.321: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.321: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.321: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.321: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.322: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.322: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.322: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.322: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.322: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.322: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.323: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.323: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.323: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.323: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.323: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.323: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.323: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.323: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.324: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.324: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.324: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.324: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.324: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.324: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.324: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.324: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.325: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.325: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.326: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.326: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.326: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.326: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.326: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.326: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.326: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.326: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.327: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.327: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.327: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.327: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.327: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.327: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.328: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.328: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.328: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.328: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.328: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.328: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.328: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.328: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.329: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.329: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.329: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.329: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.329: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.329: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.329: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.329: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.330: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.330: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.331: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.331: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.331: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.331: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.331: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.331: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.331: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.331: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.332: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.332: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.332: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.332: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.332: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.332: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.332: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.332: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.333: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.333: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.333: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.333: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.333: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.333: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.334: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.334: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.334: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.334: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.334: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.334: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.334: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.334: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.335: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.335: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.335: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.335: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.335: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.336: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.336: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.336: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.336: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.336: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.337: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.337: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.337: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.337: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.337: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.337: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.337: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.337: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.338: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.338: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.338: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.338: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.338: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.338: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.339: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.339: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.339: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.339: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.339: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.339: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.339: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.339: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.340: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.340: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.341: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.341: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.341: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.342: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.342: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.342: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.342: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.342: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.343: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.343: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.344: [vfs7552] CAPTURE_NUM_STATES entering state 4 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.344: Cleaning image 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.344: variance_after = 1526 320s 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.344: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.344: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.344: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.344: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.345: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.345: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.345: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.345: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.345: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.345: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.345: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.346: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.346: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.346: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.346: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.346: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.346: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.346: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.346: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.347: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.347: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.348: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.348: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.348: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.348: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.348: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.348: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.348: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.348: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.349: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.349: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.349: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.349: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.349: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.349: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.350: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.350: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.350: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.351: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.351: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.351: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.351: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.351: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.351: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.351: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.352: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.352: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.352: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.352: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.352: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.352: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.353: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.353: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.353: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.353: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.353: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.353: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.353: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.353: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.354: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.354: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.355: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.355: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.355: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.355: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.355: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.355: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.355: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.355: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.356: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.356: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.356: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.356: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.356: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.356: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.356: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.356: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.357: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.357: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.357: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.357: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.357: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.357: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.358: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.358: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.358: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.358: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.358: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.358: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.358: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.358: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.359: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.359: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.359: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.359: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.359: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.359: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.359: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.359: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.360: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.360: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.361: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.361: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.361: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.361: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.361: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.361: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.361: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.361: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.362: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.362: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.362: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.362: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.362: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.362: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.362: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.362: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.363: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.363: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.363: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.363: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.363: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.363: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.364: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.364: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.364: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.364: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.364: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.364: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.364: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.364: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.365: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.365: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.366: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.366: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.366: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.366: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.366: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.366: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.366: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.366: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.367: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.367: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.367: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.367: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.367: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.367: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.367: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.367: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.368: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.368: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.368: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.368: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.368: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.368: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.368: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.369: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.369: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.369: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.369: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.369: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.369: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.369: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.370: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.370: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.371: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.371: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.371: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.371: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.371: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.371: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.371: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.371: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.372: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.372: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.372: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.372: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.372: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.372: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.373: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.373: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.373: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.373: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.373: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.373: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.373: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.373: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.374: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.374: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.375: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.375: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.375: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.375: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.375: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.375: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.375: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.375: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.376: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.376: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.376: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.376: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.376: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.376: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.377: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.377: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.377: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.377: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.377: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.377: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.377: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.377: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.378: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.378: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.379: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.379: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.379: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.379: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.379: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.379: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.379: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.379: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.380: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.380: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.380: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.380: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.380: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.380: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.381: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.381: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.381: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.381: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.381: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.381: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.381: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.381: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.382: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.382: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.383: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.383: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.383: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.383: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.383: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.383: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.383: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.383: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.384: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.384: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.384: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.384: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.384: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.384: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.384: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.384: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.385: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.385: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.385: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.385: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.385: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.385: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.386: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.386: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.386: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.386: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.386: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.386: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.386: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.386: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.387: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.387: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.388: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.388: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.388: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.388: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.388: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.388: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.388: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.388: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.389: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.389: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.389: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.389: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.389: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.389: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.389: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.389: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.390: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.390: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.390: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.390: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.390: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.390: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.390: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.390: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.391: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.391: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.391: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.391: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.391: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.391: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.392: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.392: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.392: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.392: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.392: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.392: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.392: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.392: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.393: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.393: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.393: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.393: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.393: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.393: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.393: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.393: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.394: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.394: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.395: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.395: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.395: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.395: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.395: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.395: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.395: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.395: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.396: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.396: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.396: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.396: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.396: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.396: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.396: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.397: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.397: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.397: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.397: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.397: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.397: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.397: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.398: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.398: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.398: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.398: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.398: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.398: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.398: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.398: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.399: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.399: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.400: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.400: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.400: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.400: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.400: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.400: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.400: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.400: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.401: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.401: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.401: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.401: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.401: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.401: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.401: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.401: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.402: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.402: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.402: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.402: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.402: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.402: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.402: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.402: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.403: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.403: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.403: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.403: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.403: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.403: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.403: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.404: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.404: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.404: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.404: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.404: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.404: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.404: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.405: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.405: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.405: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.405: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.405: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.405: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.405: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.405: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.406: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.406: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.407: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.407: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.407: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.407: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.407: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.407: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.407: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.407: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.408: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.408: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.408: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.408: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.408: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.408: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.408: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.408: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.409: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.409: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.409: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.409: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.409: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.409: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.410: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.410: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.410: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.410: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.410: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.410: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.410: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.410: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.411: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.411: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.411: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.411: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.411: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.411: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.411: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.411: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.412: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.412: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.412: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.413: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.413: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.413: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.413: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.413: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.413: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.413: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.414: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.414: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.414: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.414: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.414: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.414: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.414: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.414: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.415: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.415: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.415: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.415: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.415: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.415: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.415: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.416: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.416: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.416: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.416: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.416: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.416: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.416: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.417: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.417: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.417: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.417: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.417: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.417: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.417: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.417: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.418: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.418: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.419: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.419: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.419: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.419: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.419: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.419: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.419: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.419: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.420: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.420: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.420: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.420: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.420: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.420: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.420: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.421: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.421: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.421: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.421: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.421: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.421: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.421: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.422: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.422: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.422: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.422: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.422: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.422: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.422: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.422: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.423: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.423: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.424: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.424: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.424: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.424: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.424: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.424: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.424: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.424: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.425: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.425: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.425: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.425: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.425: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.425: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.425: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.426: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.426: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.426: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.426: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.426: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.426: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.426: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.427: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.427: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.427: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.427: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.427: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.427: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.427: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.427: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.428: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.428: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.429: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.429: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.429: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.429: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.429: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.429: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.429: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.429: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.430: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.430: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.430: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.430: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.430: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.430: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.430: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.430: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.431: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.431: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.431: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.431: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.431: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.431: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.432: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.432: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.432: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.432: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.432: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.432: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.432: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.432: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.433: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.433: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.433: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.433: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.433: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.433: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.433: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.433: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.434: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.434: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.435: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.435: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.435: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.435: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.435: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.435: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.435: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.435: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.436: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.436: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.436: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.436: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.436: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.436: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.436: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.437: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.437: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.437: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.437: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.437: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.437: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.437: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.438: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.438: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.438: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.439: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.439: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.439: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.439: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.439: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.439: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.439: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.440: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.440: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.440: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.440: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.440: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.440: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.440: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.440: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.441: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.441: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.441: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.441: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.441: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.441: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.441: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.442: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.442: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.442: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.442: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.442: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.442: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.442: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.443: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.443: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.443: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.443: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.443: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.443: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.443: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.443: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.444: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.444: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.445: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.445: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.445: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.445: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.445: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.445: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.445: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.445: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.446: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.446: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.446: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.446: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.446: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.446: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.446: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.446: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.447: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.447: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.447: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.447: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.447: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.447: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.448: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.448: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.448: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.448: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.448: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.448: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.448: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.448: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.449: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.449: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.449: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.449: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.449: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.449: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.449: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.449: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.450: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.450: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.451: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.451: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.451: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.451: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.451: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.451: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.451: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.451: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.452: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.452: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.452: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.452: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.452: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.452: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.452: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.452: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.453: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.453: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.453: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.453: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.453: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.453: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.454: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.454: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.454: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.454: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.454: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.454: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.454: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.454: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.455: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.455: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.455: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.455: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.455: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.455: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.455: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.455: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.456: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.456: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.457: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.457: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.457: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.457: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.457: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.457: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.457: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.457: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.458: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.458: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.458: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.458: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.458: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.458: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.459: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.459: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.459: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.459: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.459: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.459: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.459: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.459: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.460: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.460: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.460: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.461: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.461: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.461: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.461: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.461: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.461: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.461: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.465: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.465: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.465: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.465: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.465: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.465: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.466: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.466: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.466: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.466: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.466: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.466: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.466: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.466: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.467: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.467: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.468: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.468: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.468: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.468: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.468: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.468: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.468: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.468: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.469: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.469: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.469: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.469: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.469: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.469: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.469: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.469: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.470: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.470: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.470: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.470: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.470: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.470: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.471: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.471: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.471: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.471: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.471: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.471: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.471: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.471: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.472: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.472: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.472: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.473: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.473: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.473: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.473: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.473: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.473: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.473: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.474: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.474: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.474: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.474: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.474: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.474: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.474: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.474: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.475: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.475: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.475: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.475: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.475: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.475: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.476: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.476: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.476: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.476: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.476: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.476: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.476: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.476: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.477: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.477: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.477: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.477: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.477: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.477: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.477: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.477: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.478: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.478: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.478: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.479: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.479: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.479: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.479: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.479: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.479: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.479: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.480: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.480: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.480: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.480: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.480: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.480: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.480: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.480: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.481: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.481: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.481: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.481: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.481: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.481: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.482: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.482: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.482: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.482: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.482: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.482: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.482: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.482: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.483: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.483: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.483: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.483: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.483: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.483: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.483: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.483: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.484: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.484: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.485: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.485: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.485: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.485: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.485: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.485: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.485: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.485: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.486: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.486: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.486: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.486: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.486: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.486: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.486: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.486: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.487: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.487: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.487: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.487: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.487: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.487: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.488: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.488: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.488: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.488: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.488: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.488: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.488: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.488: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.489: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.489: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.490: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.490: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.490: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.490: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.490: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.490: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.490: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.490: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.491: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.491: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.491: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.491: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.491: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.491: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.491: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.491: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.492: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.492: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.492: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.492: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.492: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.492: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.493: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.493: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.493: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.493: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.493: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.493: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.493: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.493: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.494: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.494: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.495: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.495: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.495: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.495: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.495: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.495: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.495: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.495: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.497: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.497: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.497: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.497: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.497: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.497: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.498: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.498: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.499: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.499: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.499: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.499: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.499: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.499: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.499: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.499: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.500: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.500: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.500: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.500: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.500: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.500: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.501: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.501: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.501: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.501: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.501: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.501: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.501: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.501: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.502: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.502: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.502: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.503: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.503: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.503: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.503: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.503: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.503: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.503: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.504: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.504: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.504: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.504: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.504: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.504: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.504: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.505: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.505: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.505: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.505: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.505: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.505: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.505: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.506: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.506: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.506: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.506: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.506: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.506: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.506: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.506: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.507: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.507: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.508: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.508: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.508: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.508: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.508: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.508: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.508: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.508: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.509: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.509: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.509: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.509: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.509: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.509: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.509: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.510: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.510: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.510: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.510: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.510: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.510: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.510: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.511: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.511: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.511: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.511: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.511: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.511: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.511: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.511: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.512: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.512: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.513: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.513: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.513: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.513: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.513: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.513: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.513: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.513: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.514: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.514: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.514: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.514: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.514: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.514: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.515: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.515: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.515: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.515: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.515: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.515: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.515: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.515: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.516: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.516: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.517: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.517: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.517: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.517: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.517: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.517: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.517: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.517: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.518: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.518: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.518: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.518: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.518: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.518: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.519: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.519: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.519: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.519: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.519: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.519: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.519: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.519: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.520: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.520: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.520: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.521: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.521: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.521: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.521: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.521: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.521: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.521: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.522: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.522: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.522: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.522: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.522: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.522: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.522: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.522: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.523: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.523: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.523: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.523: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.523: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.523: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.523: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.524: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.524: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.524: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.524: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.524: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.524: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.524: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.525: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.525: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.525: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.525: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.525: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.525: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.525: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.525: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.526: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.526: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.527: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.527: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.527: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.527: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.527: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.527: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.527: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.527: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.528: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.528: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.528: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.528: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.528: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.528: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.528: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.529: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.529: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.529: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.529: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.529: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.529: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.529: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.530: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.530: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.531: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.531: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.531: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.531: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.531: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.531: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.531: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.531: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.532: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.532: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.532: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.532: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.532: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.532: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.533: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.533: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.533: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.533: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.533: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.534: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.534: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.535: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.535: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.535: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.535: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.535: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.536: [vfs7552] CAPTURE_NUM_STATES entering state 4 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.536: Cleaning image 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.536: variance_after = 1435 320s 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.536: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.536: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.536: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.537: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.537: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.537: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.537: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.537: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.537: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.537: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.537: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.538: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.538: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.539: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.539: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.539: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.539: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.539: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.539: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.539: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.539: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.540: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.540: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.540: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.540: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.540: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.540: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.541: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.541: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.541: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.541: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.541: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.541: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.541: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.541: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.542: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.542: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.542: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.542: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.542: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.542: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.542: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.542: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.543: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.543: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.544: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.544: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.544: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.544: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.544: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.544: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.544: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.544: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.545: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.545: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.545: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.545: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.545: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.545: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.545: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.545: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.546: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.546: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.546: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.546: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.546: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.546: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.547: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.547: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.547: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.547: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.547: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.547: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.547: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.547: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.548: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.548: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.548: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.548: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.548: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.548: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.548: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.548: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.549: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.549: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.550: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.550: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.550: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.550: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.550: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.550: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.550: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.550: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.551: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.551: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.551: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.551: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.551: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.551: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.551: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.551: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.552: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.552: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.552: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.552: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.552: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.552: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.552: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.553: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.553: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.553: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.553: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.553: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.553: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.553: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.554: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.554: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.554: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.554: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.554: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.554: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.554: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.554: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.555: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.555: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.556: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.556: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.556: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.556: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.556: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.556: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.556: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.556: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.557: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.557: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.557: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.557: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.557: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.557: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.558: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.558: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.558: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.558: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.558: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.558: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.558: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.558: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.559: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.559: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.559: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.559: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.559: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.559: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.559: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.559: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.560: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.560: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.561: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.561: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.561: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.561: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.561: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.561: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.561: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.561: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.562: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.562: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.562: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.562: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.562: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.562: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.562: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.562: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.563: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.563: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.563: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.563: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.563: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.563: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.564: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.564: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.564: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.564: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.564: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.564: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.564: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.564: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.565: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.565: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.566: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.566: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.566: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.566: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.566: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.566: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.566: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.566: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.567: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.567: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.567: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.567: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.567: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.567: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.567: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.567: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.568: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.568: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.568: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.568: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.568: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.568: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.569: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.569: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.569: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.569: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.569: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.569: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.569: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.569: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.570: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.570: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.571: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.571: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.571: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.571: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.571: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.571: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.571: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.571: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.572: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.572: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.572: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.572: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.572: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.572: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.572: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.573: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.573: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.573: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.573: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.573: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.573: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.573: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.574: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.574: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.574: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.574: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.574: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.574: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.574: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.574: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.575: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.575: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.576: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.576: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.576: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.576: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.576: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.576: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.576: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.577: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.577: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.577: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.577: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.577: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.577: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.577: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.578: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.578: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.578: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.578: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.578: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.578: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.578: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.578: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.579: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.579: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.580: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.580: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.580: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.580: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.580: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.580: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.580: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.580: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.581: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.581: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.581: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.581: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.581: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.581: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.581: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.581: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.582: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.582: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.582: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.582: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.582: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.582: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.583: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.583: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.583: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.583: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.583: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.583: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.583: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.583: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.584: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.584: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.584: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.584: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.584: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.584: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.584: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.584: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.585: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.585: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.585: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.585: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.585: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.585: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.585: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.585: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.586: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.586: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.587: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.587: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.587: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.587: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.587: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.587: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.587: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.587: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.588: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.588: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.588: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.588: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.588: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.588: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.588: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.588: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.589: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.589: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.589: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.589: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.589: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.589: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.589: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.590: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.590: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.590: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.590: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.590: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.590: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.590: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.591: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.591: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.591: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.591: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.591: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.591: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.591: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.591: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.592: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.592: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.593: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.593: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.593: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.593: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.593: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.593: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.593: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.593: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.594: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.594: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.594: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.594: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.594: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.594: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.595: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.595: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.595: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.595: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.595: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.595: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.595: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.595: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.596: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.596: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.596: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.596: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.596: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.596: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.596: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.596: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.597: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.597: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.597: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.598: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.598: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.598: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.598: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.598: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.598: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.598: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.599: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.599: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.599: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.599: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.599: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.599: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.599: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.599: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.600: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.600: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.600: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.600: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.600: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.600: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.600: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.600: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.601: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.601: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.601: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.601: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.601: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.601: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.601: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.601: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.602: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.602: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.602: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.602: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.602: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.602: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.603: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.603: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.603: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.603: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.603: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.603: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.603: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.603: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.604: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.604: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.605: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.605: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.605: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.605: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.605: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.605: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.606: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.606: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.606: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.606: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.606: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.606: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.606: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.606: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.607: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.607: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.608: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.608: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.608: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.608: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.608: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.608: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.609: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.609: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.609: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.609: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.609: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.609: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.609: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.609: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.610: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.610: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.611: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.611: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.611: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.611: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.611: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.611: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.611: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.611: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.612: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.612: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.612: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.612: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.612: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.612: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.613: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.613: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.613: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.613: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.613: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.613: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.613: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.613: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.614: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.614: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.615: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.615: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.615: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.615: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.615: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.615: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.616: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.616: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.616: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.616: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.616: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.616: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.616: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.616: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.617: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.617: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.618: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.618: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.618: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.618: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.618: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.618: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.619: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.619: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.619: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.619: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.619: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.619: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.619: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.619: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.620: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.620: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.621: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.621: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.621: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.621: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.621: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.621: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.621: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.621: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.622: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.622: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.622: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.622: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.622: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.622: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.623: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.623: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.624: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.624: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.624: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.624: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.624: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.624: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.624: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.624: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.625: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.625: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.625: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.625: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.625: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.625: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.626: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.626: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.626: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.626: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.626: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.626: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.626: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.626: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.627: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.627: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.628: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.628: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.628: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.628: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.628: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.628: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.628: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.629: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.629: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.629: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.629: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.629: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.629: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.629: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.630: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.630: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.631: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.631: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.631: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.631: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.631: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.631: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.631: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.631: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.632: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.632: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.632: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.632: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.632: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.632: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.633: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.633: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.633: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.633: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.633: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.633: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.633: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.633: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.634: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.634: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.635: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.635: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.635: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.635: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.635: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.635: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.635: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.635: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.636: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.636: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.636: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.636: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.636: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.636: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.637: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.637: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.637: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.637: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.637: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.637: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.637: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.637: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.638: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.638: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.638: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.639: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.639: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.639: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.639: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.639: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.639: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.639: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.640: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.640: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.640: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.640: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.640: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.640: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.640: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.640: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.641: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.641: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.641: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.641: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.641: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.641: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.641: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.641: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.642: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.642: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.642: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.642: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.642: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.642: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.643: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.643: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.643: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.643: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.643: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.643: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.643: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.643: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.644: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.644: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.644: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.644: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.644: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.644: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.644: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.644: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.645: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.645: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.646: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.646: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.646: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.646: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.646: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.646: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.646: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.646: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.647: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.647: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.647: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.647: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.647: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.647: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.647: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.648: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.648: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.648: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.648: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.648: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.648: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.648: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.649: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.649: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.649: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.649: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.649: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.649: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.649: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.649: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.650: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.650: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.651: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.651: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.651: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.651: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.651: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.651: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.651: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.651: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.652: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.652: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.652: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.652: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.652: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.652: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.652: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.652: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.653: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.653: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.653: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.653: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.653: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.653: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.653: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.654: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.654: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.654: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.654: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.654: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.654: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.654: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.655: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.655: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.655: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.655: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.655: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.655: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.655: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.655: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.656: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.656: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.656: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.657: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.657: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.657: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.657: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.657: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.657: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.657: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.658: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.658: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.658: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.658: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.658: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.658: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.658: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.658: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.659: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.659: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.659: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.659: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.659: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.659: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.660: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.660: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.660: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.660: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.660: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.660: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.660: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.660: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.661: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.661: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.662: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.662: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.662: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.662: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.662: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.662: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.662: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.662: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.663: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.663: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.663: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.663: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.663: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.663: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.664: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.664: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.664: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.664: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.664: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.664: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.664: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.664: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.665: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.665: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.666: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.666: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.666: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.666: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.666: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.666: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.666: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.666: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.667: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.667: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.667: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.667: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.667: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.667: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.667: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.667: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.668: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.668: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.668: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.668: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.668: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.668: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.669: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.669: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.669: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.669: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.669: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.669: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.669: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.669: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.670: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.670: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.670: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.670: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.670: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.670: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.670: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.670: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.671: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.671: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.672: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.672: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.672: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.672: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.672: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.672: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.672: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.672: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.673: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.673: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.673: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.673: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.673: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.673: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.673: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.673: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.674: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.674: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.674: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.674: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.674: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.674: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.674: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.675: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.675: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.675: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.675: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.675: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.675: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.675: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.676: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.676: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.677: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.677: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.677: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.677: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.677: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.677: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.677: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.677: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.678: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.678: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.678: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.678: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.678: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.678: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.679: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.679: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.679: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.679: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.679: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.679: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.679: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.679: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.680: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.680: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.680: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.680: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.680: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.680: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.680: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.680: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.681: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.681: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.682: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.682: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.682: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.682: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.682: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.682: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.682: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.682: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.683: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.683: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.683: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.683: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.683: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.683: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.683: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.683: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.684: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.684: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.684: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.684: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.684: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.684: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.685: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.685: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.685: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.685: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.685: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.685: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.685: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.685: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.686: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.686: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.686: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.686: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.686: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.686: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.686: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.686: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.687: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.687: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.688: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.688: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.688: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.688: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.688: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.688: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.688: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.688: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.689: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.689: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.689: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.689: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.689: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.689: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.689: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.689: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.690: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.690: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.690: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.690: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.690: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.690: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.690: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.690: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.691: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.691: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.691: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.691: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.691: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.691: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.692: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.692: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.692: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.692: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.692: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.692: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.692: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.692: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.693: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.693: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.693: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.693: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.693: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.693: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.693: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.693: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.694: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.694: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.694: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.694: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.694: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.695: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.695: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.695: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.695: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.695: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.696: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.696: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.696: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.696: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.696: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.696: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.696: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.696: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.697: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.697: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.697: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.697: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.697: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.697: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.697: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.697: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.698: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.698: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.698: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.698: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.698: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.698: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.698: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.699: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.699: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.699: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.699: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.699: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.699: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.699: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.700: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.700: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.700: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.700: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.700: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.700: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.700: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.700: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.701: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.701: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.702: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.702: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.702: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.702: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.702: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.702: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.702: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.702: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.703: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.703: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.703: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.703: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.703: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.703: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.704: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.704: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.704: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.704: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.704: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.704: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.704: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.704: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.705: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.705: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.705: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.705: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.705: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.706: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.706: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.706: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.706: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.706: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.707: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.707: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.707: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.707: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.707: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.707: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.707: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.707: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.708: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.708: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.708: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.708: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.708: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.708: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.709: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.709: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.709: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.709: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.709: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.709: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.709: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.709: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.710: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.710: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.711: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.711: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.711: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.711: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.711: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.711: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.711: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.711: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.712: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.712: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.712: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.712: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.712: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.712: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.713: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.713: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.714: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.714: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.714: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.714: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.714: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.714: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.714: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.714: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.715: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.715: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.715: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.715: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.715: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.715: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.716: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.716: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.716: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.716: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.716: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.716: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.716: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.716: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.717: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.717: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.717: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.717: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.717: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.717: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.717: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.717: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.718: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.718: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.719: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.719: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.719: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.719: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.719: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.720: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.720: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.720: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.721: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.721: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.721: [vfs7552] CAPTURE_NUM_STATES entering state 4 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.721: Cleaning image 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.721: variance_after = 1425 320s 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.721: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.721: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.721: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.722: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.722: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.723: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.723: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.723: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.723: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.723: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.723: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.723: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.723: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.724: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.724: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.724: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.724: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.724: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.724: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.724: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.724: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.725: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.725: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.725: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.725: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.725: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.725: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.726: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.726: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.726: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.726: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.726: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.726: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.726: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.726: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.727: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.727: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.728: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.728: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.728: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.728: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.728: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.728: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.728: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.728: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.729: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.729: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.729: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.729: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.729: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.729: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.729: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.729: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.730: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.730: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.730: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.730: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.730: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.730: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.731: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.731: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.731: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.731: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.731: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.731: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.731: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.731: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.732: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.732: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.732: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.732: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.732: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.732: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.732: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.732: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.733: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.733: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.734: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.734: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.734: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.734: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.734: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.734: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.734: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.734: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.735: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.735: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.735: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.735: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.735: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.735: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.735: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.735: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.736: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.736: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.736: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.736: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.736: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.736: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.737: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.737: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.737: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.738: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.738: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.738: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.738: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.738: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.738: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.738: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.739: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.739: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.739: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.739: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.739: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.739: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.739: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.739: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.740: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.740: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.740: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.740: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.740: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.740: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.741: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.741: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.741: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.741: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.741: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.741: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.741: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.741: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.742: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.742: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.742: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.742: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.742: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.742: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.742: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.742: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.743: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.743: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.744: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.744: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.744: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.744: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.744: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.744: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.744: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.744: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.745: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.745: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.745: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.745: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.745: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.745: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.745: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.745: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.746: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.746: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.746: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.746: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.746: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.746: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.747: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.747: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.747: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.747: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.747: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.747: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.747: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.747: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.748: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.748: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.748: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.748: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.748: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.748: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.748: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.748: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.749: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.749: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.750: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.750: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.750: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.750: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.750: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.750: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.750: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.750: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.751: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.751: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.751: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.751: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.751: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.751: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.751: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.751: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.752: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.752: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.752: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.752: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.752: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.752: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.752: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.752: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.753: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.753: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.753: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.753: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.753: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.753: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.754: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.754: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.754: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.754: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.754: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.754: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.754: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.754: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.755: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.755: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.755: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.755: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.755: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.755: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.755: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.755: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.756: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.756: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.756: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.756: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.756: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.756: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.756: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.756: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.757: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.757: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.757: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.757: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.757: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.757: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.757: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.757: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.758: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.758: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.758: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.758: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.758: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.758: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.758: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.758: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.759: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.759: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.759: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.760: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.760: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.760: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.760: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.760: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.760: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.760: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.761: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.761: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.761: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.761: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.761: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.761: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.761: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.761: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.762: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.762: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.762: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.762: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.762: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.762: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.762: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.762: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.763: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.763: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.763: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.763: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.763: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.763: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.764: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.764: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.764: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.764: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.764: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.764: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.764: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.764: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.765: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.765: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.766: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.766: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.766: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.766: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.766: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.766: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.766: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.766: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.767: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.767: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.767: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.767: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.767: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.767: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.767: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.767: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.768: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.768: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.768: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.768: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.768: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.768: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.769: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.769: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.769: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.769: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.769: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.769: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.769: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.769: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.770: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.770: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.770: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.771: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.771: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.771: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.771: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.771: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.771: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.771: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.772: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.772: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.772: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.772: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.772: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.772: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.772: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.772: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.773: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.773: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.773: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.773: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.773: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.773: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.774: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.774: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.774: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.774: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.774: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.774: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.774: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.774: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.775: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.775: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.776: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.776: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.776: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.776: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.776: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.776: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.776: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.776: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.777: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.777: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.777: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.777: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.777: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.777: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.777: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.777: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.778: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.778: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.778: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.778: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.778: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.778: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.779: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.779: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.779: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.779: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.779: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.779: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.779: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.779: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.780: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.780: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.781: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.781: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.781: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.781: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.781: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.781: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.781: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.781: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.782: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.782: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.782: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.782: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.782: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.782: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.783: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.783: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.783: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.783: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.783: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.783: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.783: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.783: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.784: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.784: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.785: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.785: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.785: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.785: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.785: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.785: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.785: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.786: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.786: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.786: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.786: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.786: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.786: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.786: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.787: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.787: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.787: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.788: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.788: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.788: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.788: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.788: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.788: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.788: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.789: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.789: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.789: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.789: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.789: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.789: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.789: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.790: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.790: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.790: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.790: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.790: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.790: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.790: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.791: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.791: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.791: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.792: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.792: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.792: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.792: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.792: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.792: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.792: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.793: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.793: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.793: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.793: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.793: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.793: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.793: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.794: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.794: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.794: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.794: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.794: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.794: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.794: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.795: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.795: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.795: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.795: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.796: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.796: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.796: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.796: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.796: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.796: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.797: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.797: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.797: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.797: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.797: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.797: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.797: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.797: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.798: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.798: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.798: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.798: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.798: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.798: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.799: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.799: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.800: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.800: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.800: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.800: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.800: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.800: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.800: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.800: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.801: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.801: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.801: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.801: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.801: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.801: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.802: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.802: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.802: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.802: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.802: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.802: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.802: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.802: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.803: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.803: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.804: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.804: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.804: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.804: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.804: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.805: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.805: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.805: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.806: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.806: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.807: [vfs7552] CAPTURE_NUM_STATES entering state 4 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.807: Cleaning image 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.807: variance_after = 1532 320s 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.807: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.807: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.807: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.807: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.807: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.808: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.808: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.808: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.808: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.808: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.808: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.809: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.809: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.809: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.809: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.809: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.809: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.809: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.809: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.810: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.810: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.811: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.811: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.811: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.811: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.811: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.811: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.811: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.811: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.812: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.812: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.812: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.812: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.812: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.812: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.813: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.813: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.813: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.813: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.813: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.813: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.813: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.813: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.814: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.814: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.815: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.815: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.815: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.815: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.815: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.815: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.815: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.815: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.816: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.816: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.816: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.816: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.816: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.816: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.817: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.817: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.817: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.817: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.817: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.817: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.817: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.817: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.818: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.818: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.819: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.819: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.819: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.819: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.819: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.819: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.819: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.819: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.820: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.820: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.820: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.820: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.820: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.820: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.821: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.821: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.821: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.821: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.821: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.822: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.822: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.822: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.822: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.822: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.823: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.823: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.823: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.823: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.823: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.823: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.824: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.824: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.824: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.824: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.824: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.824: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.824: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.824: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.825: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.825: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.826: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.826: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.826: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.826: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.826: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.826: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.826: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.826: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.827: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.827: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.827: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.827: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.827: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.827: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.827: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.827: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.828: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.828: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.828: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.828: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.828: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.828: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.829: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.829: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.829: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.829: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.829: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.829: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.829: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.829: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.830: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.830: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.830: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.830: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.830: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.830: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.830: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.830: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.831: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.831: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.831: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.832: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.832: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.832: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.832: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.832: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.832: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.832: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.833: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.833: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.833: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.833: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.833: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.833: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.833: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.833: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.834: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.834: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.834: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.834: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.834: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.834: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.835: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.835: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.835: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.835: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.835: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.835: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.835: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.835: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.836: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.836: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.836: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.836: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.836: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.836: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.836: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.836: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.837: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.837: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.838: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.838: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.838: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.838: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.838: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.838: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.838: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.838: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.839: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.839: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.839: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.839: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.839: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.839: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.840: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.840: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.840: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.840: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.840: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.840: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.840: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.840: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.841: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.841: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.842: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.842: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.842: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.842: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.842: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.842: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.842: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.842: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.843: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.843: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.843: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.843: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.843: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.843: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.843: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.843: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.844: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.844: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.844: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.844: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.844: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.844: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.844: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.844: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.845: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.845: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.845: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.845: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.845: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.845: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.846: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.846: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.846: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.846: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.846: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.846: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.846: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.846: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.847: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.847: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.847: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.847: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.847: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.847: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.847: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.847: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.848: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.848: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.849: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.849: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.849: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.849: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.849: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.849: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.849: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.849: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.850: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.850: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.850: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.850: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.850: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.850: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.851: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.851: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.851: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.851: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.851: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.851: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.851: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.851: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.852: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.852: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.852: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.852: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.852: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.852: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.852: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.852: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.853: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.853: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.854: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.854: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.854: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.854: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.854: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.854: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.854: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.854: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.855: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.855: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.855: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.855: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.855: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.855: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.855: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.855: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.856: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.856: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.856: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.857: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.857: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.857: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.857: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.857: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.858: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.858: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.859: [vfs7552] CAPTURE_NUM_STATES entering state 4 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.859: Cleaning image 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.859: variance_after = 1691 320s 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.859: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.859: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.859: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.859: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.859: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.860: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.860: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.860: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.860: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.860: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.860: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.861: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.861: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.861: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.861: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.861: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.861: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.861: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.861: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.862: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.862: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.862: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.863: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.863: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.863: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.863: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.863: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.863: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.863: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.864: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.864: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.864: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.864: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.864: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.864: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.864: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.864: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.865: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.865: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.865: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.865: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.865: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.865: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.865: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.865: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.866: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.866: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.866: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.866: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.866: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.866: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.867: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.867: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.867: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.867: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.867: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.867: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.867: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.867: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.868: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.868: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.868: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.868: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.868: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.868: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.868: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.868: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.869: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.869: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.870: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.870: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.870: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.870: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.870: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.870: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.870: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.870: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.871: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.871: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.871: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.871: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.871: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.871: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.871: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.871: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.872: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.872: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.872: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.872: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.872: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.872: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.873: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.873: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.873: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.873: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.873: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.873: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.873: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.873: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.874: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.874: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.874: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.874: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.874: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.874: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.874: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.874: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.875: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.875: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.876: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.876: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.876: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.876: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.876: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.876: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.876: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.876: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.877: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.877: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.877: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.877: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.877: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.877: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.877: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.877: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.878: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.878: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.878: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.878: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.878: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.878: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.879: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.879: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.879: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.879: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.879: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.879: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.879: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.879: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.880: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.880: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.880: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.880: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.880: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.880: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.880: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.880: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.881: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.881: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.882: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.882: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.882: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.882: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.882: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.882: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.882: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.882: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.883: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.883: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.883: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.883: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.883: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.883: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.884: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.884: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.884: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.884: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.884: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.884: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.884: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.884: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.885: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.885: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.885: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.885: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.885: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.885: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.885: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.885: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.886: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.886: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.886: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.887: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.887: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.887: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.887: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.887: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.887: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.887: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.888: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.888: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.888: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.888: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.888: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.888: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.888: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.888: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.889: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.889: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.889: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.889: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.889: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.889: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.890: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.890: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.890: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.890: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.890: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.890: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.890: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.890: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.891: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.891: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.891: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.891: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.891: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.891: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.891: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.891: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.892: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.892: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.893: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.893: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.893: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.893: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.893: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.893: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.893: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.893: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.894: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.894: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.894: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.894: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.894: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.894: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.894: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.894: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.895: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.895: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.895: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.895: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.895: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.895: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.895: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.896: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.896: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.896: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.896: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.896: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.896: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.896: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.897: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.897: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.897: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.897: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.897: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.897: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.897: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.897: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.898: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.898: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.898: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.899: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.899: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.899: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.899: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.899: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.899: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.899: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.900: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.900: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.900: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.900: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.900: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.900: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.900: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.900: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.901: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.901: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.901: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.901: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.901: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.901: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.901: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.901: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.902: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.902: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.902: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.902: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.902: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.902: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.903: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.903: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.903: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.903: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.904: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.904: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.904: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.904: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.904: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.904: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.905: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.905: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.905: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.905: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.905: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.905: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.905: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.905: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.906: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.906: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.906: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.906: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.906: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.906: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.906: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.907: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.907: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.907: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.907: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.907: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.907: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.907: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.908: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.908: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.908: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.908: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.908: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.909: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.909: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.910: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.910: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.910: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.910: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.910: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.911: [vfs7552] CAPTURE_NUM_STATES entering state 4 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.911: Cleaning image 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.911: variance_after = 1845 320s 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.911: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.911: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.911: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.912: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.912: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.912: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.912: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.912: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.912: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.912: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.912: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.913: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.913: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.914: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.914: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.914: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.914: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.914: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.914: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.914: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.914: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.915: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.915: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.915: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.915: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.915: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.915: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.916: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.916: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.916: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.916: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.916: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.916: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.916: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.916: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.917: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.917: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.918: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.918: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.918: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.918: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.918: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.918: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.919: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.919: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.919: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.919: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.919: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.919: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.919: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.919: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.920: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.920: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.921: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.921: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.921: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.921: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.921: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.921: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.921: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.922: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.922: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.922: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.922: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.922: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.922: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.922: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.923: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.923: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.923: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.923: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.923: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.923: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.923: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.923: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.924: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.924: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.924: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.924: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.924: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.924: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.924: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.924: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.925: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.925: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.926: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.926: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.926: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.926: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.926: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.926: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.926: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.926: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.927: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.927: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.927: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.927: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.927: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.927: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.927: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.927: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.928: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.928: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.928: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.928: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.928: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.928: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.929: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.929: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.929: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.929: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.929: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.929: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.929: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.929: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.930: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.930: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.930: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.930: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.930: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.930: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.930: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.930: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.931: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.931: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.931: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.932: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.932: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.932: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.932: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.932: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.932: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.932: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.932: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.932: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.933: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.933: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.933: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.933: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.933: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.933: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.934: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.934: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.934: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.934: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.934: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.934: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.934: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.934: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.935: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.935: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.935: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.935: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.935: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.935: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.935: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.935: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.936: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.936: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.936: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.936: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.936: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.936: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.937: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.937: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.937: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.937: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.937: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.937: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.937: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.937: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.938: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.938: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.938: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.938: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.938: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.938: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.938: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.938: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.939: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.939: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.939: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.939: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.939: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.939: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.939: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.939: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.940: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.940: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.940: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.940: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.940: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.940: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.940: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.940: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.941: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.941: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.942: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.942: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.942: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.942: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.942: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.942: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.942: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.942: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.943: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.943: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.943: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.943: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.943: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.943: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.943: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.943: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.944: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.944: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.944: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.944: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.944: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.944: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.944: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.944: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.945: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.945: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.945: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.945: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.945: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.945: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.945: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.945: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.946: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.946: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.946: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.946: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.946: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.946: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.946: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.946: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.947: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.947: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.947: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.947: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.947: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.947: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.948: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.948: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.948: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.948: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.948: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.948: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.948: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.948: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.949: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.949: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.949: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.949: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.949: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.949: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.949: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.949: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.950: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.950: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.950: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.950: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.950: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.950: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.950: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.950: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.951: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.951: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.951: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.952: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.952: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.952: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.952: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.952: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.952: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.952: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.953: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.953: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.953: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.953: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.953: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.953: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.953: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.953: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.954: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.954: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.954: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.954: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.954: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.954: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.954: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.954: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.955: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.955: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.955: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.955: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.955: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.955: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.955: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.955: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.956: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.956: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.956: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.956: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.956: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.956: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.957: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.957: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.957: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.957: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.957: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.957: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.957: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.957: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.958: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.958: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.958: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.958: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.958: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.958: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.958: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.958: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.959: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.959: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.959: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.959: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.959: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.959: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.959: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.959: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.960: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.960: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.960: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.960: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.960: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.960: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.960: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.960: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.961: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.961: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.962: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.962: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.962: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.962: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.962: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.962: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.962: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.962: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.963: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.963: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.963: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.963: [vfs7552] CAPTURE_NUM_STATES entering state 0 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.963: [vfs7552] QUERY DATA READY entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.963: Sending vfs7552_is_image_ready 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.963: [vfs7552] QUERY DATA READY entering state 1 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.963: Receiving 64 bytes 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.964: Got 6 bytes out of 64 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.964: [vfs7552] QUERY DATA READY completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.964: [vfs7552] CAPTURE_NUM_STATES entering state 1 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.964: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.964: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.964: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.964: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.964: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.965: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.965: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.965: Sending vfs7552_read_image_chunk 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.966: [vfs7552] REQUEST CHUNK completed successfully 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.966: [vfs7552] CAPTURE_NUM_STATES entering state 3 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.966: [vfs7552] CAPTURE_NUM_STATES entering state 2 320s (process:2572): libfprint-SSM-DEBUG: 05:02:19.966: [vfs7552] REQUEST CHUNK entering state 0 320s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.966: Sending vfs7552_read_image_chunk 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.967: [vfs7552] REQUEST CHUNK completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.967: [vfs7552] CAPTURE_NUM_STATES entering state 3 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.967: [vfs7552] CAPTURE_NUM_STATES entering state 4 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.967: Cleaning image 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.967: variance_after = 2342 321s 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.967: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.967: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.967: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.968: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.968: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.969: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.969: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.969: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.969: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.969: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.969: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.969: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.969: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.970: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.970: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.970: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.970: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.970: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.970: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.970: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.970: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.971: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.971: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.971: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.971: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.971: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.971: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.971: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.972: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.972: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.972: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.972: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.972: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.972: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.972: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.973: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.973: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.973: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.973: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.973: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.973: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.973: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.973: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.974: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.974: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.974: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.974: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.974: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.974: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.974: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.974: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.975: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.975: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.976: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.976: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.976: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.976: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.976: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.976: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.976: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.976: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.977: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.977: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.977: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.977: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.977: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.977: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.977: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.977: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.978: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.978: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.978: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.978: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.978: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.978: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.978: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.978: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.979: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.979: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.979: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.979: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.979: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.979: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.979: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.980: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.980: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.980: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.980: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.980: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.980: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.980: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.981: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.981: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.981: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.981: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.981: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.981: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.981: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.981: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.982: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.982: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.982: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.982: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.982: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.982: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.982: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.982: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.983: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.983: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.983: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.984: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.984: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.984: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.984: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.984: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.984: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.984: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.985: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.985: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.985: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.985: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.985: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.985: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.985: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.985: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.986: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.986: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.986: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.986: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.986: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.986: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.986: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.986: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.987: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.987: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.987: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.987: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.987: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.987: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.987: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.988: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.988: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.988: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.988: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.988: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.988: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.988: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.989: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.989: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.989: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.989: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.989: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.989: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.989: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.989: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.990: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.990: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.990: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.990: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.990: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.990: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.990: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.990: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.991: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.991: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.991: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.991: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.991: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.991: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.991: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.991: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.992: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.992: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.992: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.992: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.992: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.992: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.992: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.993: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.993: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.993: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.994: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.994: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.994: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.994: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.994: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.994: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.994: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.994: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.995: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.995: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.995: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.995: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.995: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.995: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.996: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.996: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.996: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.996: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.996: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.996: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.996: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.996: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.997: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.997: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.997: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.997: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.997: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.997: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.997: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.997: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.998: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.998: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.999: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.999: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.999: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.999: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.999: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.999: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:19.999: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:19.999: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.000: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.000: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.000: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.000: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.000: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.000: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.000: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.000: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.001: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.001: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.001: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.001: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.001: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.001: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.001: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.001: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.002: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.002: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.002: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.002: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.002: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.002: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.003: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.003: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.003: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.003: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.003: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.003: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.003: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.003: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.004: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.004: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.004: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.004: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.004: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.004: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.004: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.004: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.005: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.005: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.005: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.005: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.005: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.005: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.005: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.005: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.006: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.006: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.006: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.006: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.007: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.007: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.007: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.007: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.007: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.007: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.008: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.008: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.008: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.008: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.008: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.008: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.008: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.008: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.009: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.009: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.009: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.009: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.009: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.009: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.010: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.010: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.010: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.010: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.010: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.010: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.010: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.010: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.011: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.011: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.011: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.012: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.012: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.012: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.012: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.012: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.012: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.012: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.013: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.013: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.013: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.013: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.013: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.013: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.013: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.013: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.014: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.014: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.014: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.014: [vfs7552] CAPTURE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.014: [vfs7552] QUERY DATA READY entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.014: Sending vfs7552_is_image_ready 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.014: [vfs7552] QUERY DATA READY entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.014: Receiving 64 bytes 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.015: Got 6 bytes out of 64 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.015: [vfs7552] QUERY DATA READY completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.015: [vfs7552] CAPTURE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.015: [vfs7552] CAPTURE_NUM_STATES entering state 2 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.015: [vfs7552] REQUEST CHUNK entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.015: Sending vfs7552_read_image_chunk 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.016: [vfs7552] REQUEST CHUNK completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.016: [vfs7552] CAPTURE_NUM_STATES entering state 3 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.016: [vfs7552] CAPTURE_NUM_STATES entering state 2 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.016: [vfs7552] REQUEST CHUNK entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.016: Sending vfs7552_read_image_chunk 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.017: [vfs7552] REQUEST CHUNK completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.017: [vfs7552] CAPTURE_NUM_STATES entering state 3 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.018: [vfs7552] CAPTURE_NUM_STATES entering state 2 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.018: [vfs7552] REQUEST CHUNK entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.018: Sending vfs7552_read_image_chunk 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.018: [vfs7552] REQUEST CHUNK completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.018: [vfs7552] CAPTURE_NUM_STATES entering state 3 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.019: [vfs7552] CAPTURE_NUM_STATES entering state 4 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.019: Cleaning image 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.019: variance_after = 16 321s 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.019: [vfs7552] CAPTURE_NUM_STATES completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.019: [vfs7552] DEACTIVATE_NUM_STATES entering state 0 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.029: [vfs7552] DEACTIVATE_NUM_STATES entering state 1 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.029: [vfs7552] STOP CAPTURE entering state 0 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.029: Sending vfs7552_cmd_04 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.029: [vfs7552] STOP CAPTURE entering state 1 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.029: Receiving 64 bytes 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.030: [vfs7552] STOP CAPTURE entering state 2 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.030: Sending vfs7552_cmd_52 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.030: [vfs7552] STOP CAPTURE entering state 3 321s (process:2572): libfprint-vfs7552-DEBUG: 05:02:20.030: Receiving 64 bytes 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.031: [vfs7552] STOP CAPTURE completed successfully 321s (process:2572): libfprint-SSM-DEBUG: 05:02:20.031: [vfs7552] DEACTIVATE_NUM_STATES completed successfully 321s (process:2572): libfprint-device-DEBUG: 05:02:20.031: Device reported finger status change: FP_FINGER_STATUS_NONE 321s (process:2572): libfprint-image_device-DEBUG: 05:02:20.031: Image device reported finger status: off 321s (process:2572): libfprint-image_device-DEBUG: 05:02:20.031: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 321s (process:2572): libfprint-image_device-DEBUG: 05:02:20.031: Deactivating image device 321s (process:2572): libfprint-image_device-DEBUG: 05:02:20.031: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 321s (process:2572): libfprint-image_device-DEBUG: 05:02:20.031: Image device deactivation completed 321s (process:2572): libfprint-image_device-DEBUG: 05:02:20.031: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 321s (process:2572): libfprint-device-DEBUG: 05:02:20.031: Device reported capture completion 321s (process:2572): libfprint-device-DEBUG: 05:02:20.031: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 321s (process:2572): libfprint-device-DEBUG: 05:02:20.031: Updated temperature model after 3.06 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 321s (process:2572): libfprint-image_device-DEBUG: 05:02:20.032: Image device close completed 321s (process:2572): libfprint-device-DEBUG: 05:02:20.032: Device reported close completion 321s (process:2572): libfprint-device-DEBUG: 05:02:20.032: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s (process:2572): libfprint-device-DEBUG: 05:02:20.032: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 321s ** (umockdev-run:2568): DEBUG: 05:02:20.126: umockdev.vala:154: Removing test bed /tmp/umockdev.Z3V212 321s (umockdev-run:2568): GLib-DEBUG: 05:02:20.130: unsetenv() is not thread-safe and should not be used after threads are created 321s Comparing PNGs /tmp/libfprint-umockdev-test-2473lmi5/capture.png and /usr/share/installed-tests/libfprint-2/vfs7552/capture.png 321s PASS: libfprint-2/driver-vfs7552.test 321s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 321s TAP version 14 321s # random seed: R02S764f7cf822261c523a691d17e4fa3fe5 321s 1..14 321s # Start of device tests 321s # Start of async tests 321s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 321s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 321s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xeca9a7292660, GType is 203387745817200 321s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 321s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 321s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 321s # libfprint-context-DEBUG: created 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 321s # 321s # libfprint-device-DEBUG: Device reported probe completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 321s # 321s # libfprint-device-DEBUG: Device reported open completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 321s # 321s # libfprint-device-DEBUG: Device reported close completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s ok 1 /device/async/open 321s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 321s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 321s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xeca9a7292660, GType is 203387745817200 321s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 321s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 321s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 321s # libfprint-context-DEBUG: created 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 321s # 321s # libfprint-device-DEBUG: Device reported probe completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 321s # 321s # libfprint-device-DEBUG: Device reported open completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 321s # 321s # libfprint-device-DEBUG: Device reported close completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s ok 2 /device/async/close 321s # End of async tests 321s # Start of sync tests 321s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 321s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 321s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xeca9a7292660, GType is 203387745817200 321s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 321s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 321s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 321s # libfprint-context-DEBUG: created 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 321s # 321s # libfprint-device-DEBUG: Device reported probe completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 321s # 321s # libfprint-device-DEBUG: Device reported open completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 321s # 321s # libfprint-device-DEBUG: Device reported close completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s ok 3 /device/sync/open 321s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 321s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 321s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xeca9a7292660, GType is 203387745817200 321s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 321s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 321s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 321s # libfprint-context-DEBUG: created 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 321s # 321s # libfprint-device-DEBUG: Device reported probe completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 321s # 321s # libfprint-device-DEBUG: Device reported open completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 321s # 321s # libfprint-device-DEBUG: Device reported close completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s ok 4 /device/sync/close 321s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 321s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 321s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xeca9a7292660, GType is 203387745817200 321s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 321s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 321s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 321s # libfprint-context-DEBUG: created 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 321s # 321s # libfprint-device-DEBUG: Device reported probe completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 321s # 321s # libfprint-device-DEBUG: Device reported open completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 321s # 321s # libfprint-device-DEBUG: Device reported close completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s ok 5 /device/sync/get_driver 321s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 321s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 321s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xeca9a7292660, GType is 203387745817200 321s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 321s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 321s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 321s # libfprint-context-DEBUG: created 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 321s # 321s # libfprint-device-DEBUG: Device reported probe completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 321s # 321s # libfprint-device-DEBUG: Device reported open completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 321s # 321s # libfprint-device-DEBUG: Device reported close completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s ok 6 /device/sync/get_device_id 321s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 321s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 321s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xeca9a7292660, GType is 203387745817200 321s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 321s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 321s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 321s # libfprint-context-DEBUG: created 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 321s # 321s # libfprint-device-DEBUG: Device reported probe completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 321s # 321s # libfprint-device-DEBUG: Device reported open completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 321s # 321s # libfprint-device-DEBUG: Device reported close completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s ok 7 /device/sync/get_name 321s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 321s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 321s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xeca9a7292660, GType is 203387745817200 321s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 321s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 321s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 321s # libfprint-context-DEBUG: created 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 321s # 321s # libfprint-device-DEBUG: Device reported probe completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 321s # 321s # libfprint-device-DEBUG: Device reported open completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 321s # 321s # libfprint-device-DEBUG: Device reported close completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s ok 8 /device/sync/get_scan_type 321s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 321s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 321s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xeca9a7292660, GType is 203387745817200 321s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 321s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 321s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 321s # libfprint-context-DEBUG: created 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 321s # 321s # libfprint-device-DEBUG: Device reported probe completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 321s # 321s # libfprint-device-DEBUG: Device reported open completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 321s # 321s # libfprint-device-DEBUG: Device reported close completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s ok 9 /device/sync/get_nr_enroll_stages 321s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 321s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 321s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xeca9a7292660, GType is 203387745817200 321s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 321s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 321s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 321s # libfprint-context-DEBUG: created 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 321s # 321s # libfprint-device-DEBUG: Device reported probe completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 321s # 321s # libfprint-device-DEBUG: Device reported open completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 321s # 321s # libfprint-device-DEBUG: Device reported close completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s ok 10 /device/sync/supports_identify 321s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 321s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 321s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xeca9a7292660, GType is 203387745817200 321s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 321s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 321s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 321s # libfprint-context-DEBUG: created 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 321s # 321s # libfprint-device-DEBUG: Device reported probe completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 321s # 321s # libfprint-device-DEBUG: Device reported open completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 321s # 321s # libfprint-device-DEBUG: Device reported close completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s ok 11 /device/sync/supports_capture 321s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 321s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 321s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xeca9a7292660, GType is 203387745817200 321s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 321s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 321s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 321s # libfprint-context-DEBUG: created 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 321s # 321s # libfprint-device-DEBUG: Device reported probe completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 321s # 321s # libfprint-device-DEBUG: Device reported open completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 321s # 321s # libfprint-device-DEBUG: Device reported close completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s ok 12 /device/sync/has_storage 321s # Start of open tests 321s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 321s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 321s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xeca9a7292660, GType is 203387745817200 321s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 321s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 321s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 321s # libfprint-context-DEBUG: created 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 321s # 321s # libfprint-device-DEBUG: Device reported probe completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 321s # 321s # libfprint-device-DEBUG: Device reported open completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 321s # 321s # libfprint-device-DEBUG: Device reported close completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s ok 13 /device/sync/open/notify 321s # End of open tests 321s # Start of close tests 321s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1) 321s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so 321s # libfprint-tod-DEBUG: Found TOD entry point symbol 0xeca9a7292660, GType is 203387745817200 321s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging) 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0003 321s # libfprint-context-DEBUG: No driver found for USB device 0627:0001 321s # libfprint-context-DEBUG: No driver found for USB device 1D6B:0002 321s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes 321s # libfprint-context-DEBUG: created 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE 321s # 321s # libfprint-device-DEBUG: Device reported probe completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN 321s # 321s # libfprint-device-DEBUG: Device reported open completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE 321s # 321s # libfprint-device-DEBUG: Device reported close completion 321s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s ok 14 /device/sync/close/notify 321s # End of close tests 321s # End of sync tests 321s # End of device tests 321s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test 321s Running test: libfprint-2/driver-uru4000-4500.test 321s ** (umockdev-run:2613): DEBUG: 05:02:20.261: umockdev.vala:127: Created udev test bed /tmp/umockdev.U5LE22 321s ** (umockdev-run:2613): DEBUG: 05:02:20.262: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 321s ** (umockdev-run:2613): DEBUG: 05:02:20.263: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 321s ** (umockdev-run:2613): DEBUG: 05:02:20.265: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.U5LE22/dev/bus/usb/001/050 321s ** (umockdev-run:2613): DEBUG: 05:02:20.265: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 321s ** (umockdev-run:2613): DEBUG: 05:02:20.266: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 321s ** (umockdev-run:2613): DEBUG: 05:02:20.268: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.U5LE22/dev/bus/usb/001/001 321s ** (umockdev-run:2613): DEBUG: 05:02:20.269: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 321s ** (umockdev-run:2613): DEBUG: 05:02:20.269: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 321s (process:2617): libfprint-context-DEBUG: 05:02:20.383: Initializing FpContext (libfprint version 1.94.9+tod1) 321s (process:2617): libfprint-tod-DEBUG: 05:02:20.383: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 321s (process:2617): libfprint-context-DEBUG: 05:02:20.386: No driver found for USB device 1D6B:0002 321s (process:2617): libfprint-device-DEBUG: 05:02:20.386: Device reported probe completion 321s (process:2617): libfprint-device-DEBUG: 05:02:20.386: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s (process:2617): libfprint-device-DEBUG: 05:02:20.386: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.391: Image device open completed 321s (process:2617): libfprint-device-DEBUG: 05:02:20.391: Device reported open completion 321s (process:2617): libfprint-device-DEBUG: 05:02:20.391: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s (process:2617): libfprint-device-DEBUG: 05:02:20.391: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s (process:2617): libfprint-device-DEBUG: 05:02:20.391: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.391: Activating image device 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.391: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.392: [uru4000] INIT_NUM_STATES entering state 0 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.392: read 1 regs at 7 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.392: reg value 1 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.393: [uru4000] INIT_NUM_STATES entering state 1 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.393: [uru4000] INIT_NUM_STATES entering state 3 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.393: set 81 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.393: [uru4000] INIT_NUM_STATES entering state 4 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.393: [uru4000] POWERUP_NUM_STATES entering state 0 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.393: [uru4000] POWERUP_NUM_STATES entering state 1 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.393: set 01 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.394: recv irq type 56aa 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.394: early scanpwr interrupt 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.395: [uru4000] POWERUP_NUM_STATES entering state 2 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.395: read 1 regs at 7 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.395: reg value 1 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.395: [uru4000] POWERUP_NUM_STATES entering state 3 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.395: [uru4000] POWERUP_NUM_STATES completed successfully 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.395: [uru4000] INIT_NUM_STATES entering state 5 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.395: [uru4000] INIT_NUM_STATES entering state 6 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.395: [uru4000] INIT_NUM_STATES entering state 7 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.395: read 16 regs at f0 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.396: reg value 1a 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.396: [uru4000] INIT_NUM_STATES entering state 8 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.396: Versions 0010 and 0115 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.396: [uru4000] INIT_NUM_STATES completed successfully 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.396: Image device activation completed 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.396: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.396: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.396: wait finger on 321s (process:2617): libfprint-device-DEBUG: 05:02:20.396: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.397: recv irq type 56aa 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.398: recv irq type 56aa 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.398: recv irq type 0101 321s (process:2617): libfprint-device-DEBUG: 05:02:20.398: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.398: Image device reported finger status: on 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.398: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.398: starting capture 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.398: Image encryption seed: 1374298404 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.398: [uru4000] IMAGING_NUM_STATES entering state 0 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.400: [uru4000] IMAGING_NUM_STATES entering state 1 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.401: hw header lines 289 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.401: dev2: 11240 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.401: image seems to be encrypted 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.401: [uru4000] IMAGING_NUM_STATES entering state 2 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.401: read 4 regs at 34 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: reg value f2 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.402: [uru4000] IMAGING_NUM_STATES entering state 3 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: encryption id 00 -> key 544409d6 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: 0 02 72 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: decoding 72 lines 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: 1 00 1 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: skipping 1 lines 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: 2 02 49 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: decoding 49 lines 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: 3 01 1 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: skipping 1 lines 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: 4 00 1 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: skipping 1 lines 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: 5 02 49 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: decoding 49 lines 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: 6 00 1 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: skipping 1 lines 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: 7 02 116 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.402: decoding 116 lines 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.403: [uru4000] IMAGING_NUM_STATES entering state 4 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.403: Image device captured an image 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.403: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 321s (process:2617): libfprint-device-DEBUG: 05:02:20.403: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2617): libfprint-SSM-DEBUG: 05:02:20.404: [uru4000] IMAGING_NUM_STATES completed successfully 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.404: await finger off 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.406: recv irq type 0200 321s (process:2617): libfprint-device-DEBUG: 05:02:20.406: Device reported finger status change: FP_FINGER_STATUS_NONE 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.406: Image device reported finger status: off 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.406: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.406: Deactivating image device 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.406: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.406: deactivating 321s (process:2617): libfprint-uru4000-DEBUG: 05:02:20.407: cancelled 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.407: Image device deactivation completed 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.407: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 321s (process:2617): libfprint-image-DEBUG: 05:02:20.426: Minutiae scan completed in 0.022299 secs 321s (process:2617): libfprint-device-DEBUG: 05:02:20.426: Device reported capture completion 321s (process:2617): libfprint-device-DEBUG: 05:02:20.426: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 321s (process:2617): libfprint-device-DEBUG: 05:02:20.426: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 321s (process:2617): libfprint-image_device-DEBUG: 05:02:20.426: Image device close completed 321s (process:2617): libfprint-device-DEBUG: 05:02:20.426: Device reported close completion 321s (process:2617): libfprint-device-DEBUG: 05:02:20.427: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 321s (process:2617): libfprint-device-DEBUG: 05:02:20.427: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 321s ** (umockdev-run:2613): DEBUG: 05:02:20.610: umockdev.vala:154: Removing test bed /tmp/umockdev.U5LE22 321s (umockdev-run:2613): GLib-DEBUG: 05:02:20.614: unsetenv() is not thread-safe and should not be used after threads are created 321s Comparing PNGs /tmp/libfprint-umockdev-test-0b0zeu37/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-4500/capture.png 321s PASS: libfprint-2/driver-uru4000-4500.test 321s Running test: libfprint-2/driver-egismoc-0586.test 321s ** (umockdev-run:2626): DEBUG: 05:02:20.718: umockdev.vala:127: Created udev test bed /tmp/umockdev.DWU412 321s ** (umockdev-run:2626): DEBUG: 05:02:20.718: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7 321s ** (umockdev-run:2626): DEBUG: 05:02:20.720: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb) 321s ** (umockdev-run:2626): DEBUG: 05:02:20.722: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DWU412/dev/bus/usb/001/021 321s ** (umockdev-run:2626): DEBUG: 05:02:20.722: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 321s ** (umockdev-run:2626): DEBUG: 05:02:20.723: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 321s ** (umockdev-run:2626): DEBUG: 05:02:20.725: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.DWU412/dev/bus/usb/001/001 321s ** (umockdev-run:2626): DEBUG: 05:02:20.726: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 321s ** (umockdev-run:2626): DEBUG: 05:02:20.726: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 321s (process:2630): libfprint-context-DEBUG: 05:02:20.834: Initializing FpContext (libfprint version 1.94.9+tod1) 321s (process:2630): libfprint-tod-DEBUG: 05:02:20.834: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.836: 98755113: ../libfprint/drivers/egismoc/egismoc.c:1597 321s (process:2630): libfprint-context-DEBUG: 05:02:20.837: No driver found for USB device 1D6B:0002 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.837: egismoc_probe enter --> 321s (process:2630): libfprint-device-DEBUG: 05:02:20.839: Device reported probe completion 321s (process:2630): libfprint-device-DEBUG: 05:02:20.839: Completing action FPI_DEVICE_ACTION_PROBE in idle! 321s (process:2630): libfprint-device-DEBUG: 05:02:20.839: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.840: Opening device 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.841: [egismoc] DEV_INIT_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.841: [egismoc] DEV_INIT_STATES entering state 1 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.842: [egismoc] DEV_INIT_STATES entering state 2 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.843: [egismoc] DEV_INIT_STATES entering state 3 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.844: [egismoc] DEV_INIT_STATES entering state 4 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.845: [egismoc] DEV_INIT_STATES entering state 5 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.845: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.845: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.845: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.845: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.846: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.847: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.847: Firmware version callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.847: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.847: Device firmware version is 9050.6.2.56 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.847: [egismoc] DEV_INIT_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.847: Task SSM done 321s (process:2630): libfprint-device-DEBUG: 05:02:20.847: Device reported open completion 321s (process:2630): libfprint-device-DEBUG: 05:02:20.847: Completing action FPI_DEVICE_ACTION_OPEN in idle! 321s (process:2630): libfprint-device-DEBUG: 05:02:20.847: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.847: List 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.847: [egismoc] LIST_STATES entering state 0 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.847: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.847: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.847: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.848: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.849: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.849: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.849: List callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.849: Device fingerprint 1: FP1-20240417-7-67C37FA4-root 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.849: Number of currently enrolled fingerprints on the device is 1 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.849: [egismoc] LIST_STATES entering state 1 321s (process:2630): libfprint-device-DEBUG: 05:02:20.849: Device reported listing completion 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.849: [egismoc] LIST_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.849: Task SSM done 321s (process:2630): libfprint-device-DEBUG: 05:02:20.849: Completing action FPI_DEVICE_ACTION_LIST in idle! 321s (process:2630): libfprint-device-DEBUG: 05:02:20.849: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.849: Clear storage 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.849: [egismoc] DELETE_STATES entering state 0 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.849: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.849: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.849: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.850: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.851: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.851: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.851: List callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.851: Device fingerprint 1: FP1-20240417-7-67C37FA4-root 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.851: Number of currently enrolled fingerprints on the device is 1 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.851: [egismoc] DELETE_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.851: Get delete command 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.851: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.851: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.851: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.852: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.853: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.853: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.853: Delete callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.853: Response prefix valid: yes 321s (process:2630): libfprint-device-DEBUG: 05:02:20.853: Device reported deletion completion 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.853: [egismoc] DELETE_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.853: Task SSM done 321s (process:2630): libfprint-device-DEBUG: 05:02:20.853: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 321s (process:2630): libfprint-device-DEBUG: 05:02:20.853: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.853: List 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.853: [egismoc] LIST_STATES entering state 0 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.853: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.853: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.853: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.853: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.854: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.854: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.854: List callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.854: Number of currently enrolled fingerprints on the device is 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.854: [egismoc] LIST_STATES entering state 1 321s (process:2630): libfprint-device-DEBUG: 05:02:20.854: Device reported listing completion 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.854: [egismoc] LIST_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.854: Task SSM done 321s (process:2630): libfprint-device-DEBUG: 05:02:20.854: Completing action FPI_DEVICE_ACTION_LIST in idle! 321s (process:2630): libfprint-device-DEBUG: 05:02:20.854: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s (process:2630): libfprint-device-DEBUG: 05:02:20.855: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.855: Enroll 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.855: [egismoc] ENROLL_STATES entering state 0 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.855: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.855: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.855: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.856: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.856: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.856: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.856: List callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.856: Number of currently enrolled fingerprints on the device is 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.856: [egismoc] ENROLL_STATES entering state 1 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.856: [egismoc] ENROLL_STATES entering state 2 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.856: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.856: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.856: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.857: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.858: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.858: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.858: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.858: [egismoc] ENROLL_STATES entering state 3 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.858: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.858: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.858: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.859: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.859: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.859: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.859: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.859: [egismoc] ENROLL_STATES entering state 4 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.859: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.859: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.860: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.860: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.860: [egismoc] ENROLL_STATES entering state 5 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.860: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.860: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.860: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.860: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.861: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.861: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.861: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.861: [egismoc] ENROLL_STATES entering state 6 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.861: Get check command 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.861: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.861: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.861: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.861: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.862: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.862: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.862: Enroll check callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.862: Response suffix valid: yes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.862: [egismoc] ENROLL_STATES entering state 7 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.862: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.862: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.862: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.862: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.863: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.863: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.863: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.863: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.863: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.863: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.863: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.864: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.864: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.864: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.864: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.864: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.864: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.864: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.864: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.865: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.866: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.866: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.866: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.866: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.866: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.866: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.867: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.867: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.867: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.867: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.867: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.867: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.867: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.868: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.868: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.868: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.868: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.868: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.868: Partial capture successful. Please touch the sensor again (1/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.868: Device reported enroll progress, reported 1 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.868: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.868: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.868: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.868: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.869: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.870: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.870: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.870: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.870: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.870: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.870: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.870: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.870: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.871: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.871: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.871: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.871: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.871: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.871: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.872: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.872: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.872: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.872: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.872: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.872: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.873: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.873: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.873: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.873: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.873: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.873: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.873: Partial capture successful. Please touch the sensor again (2/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.873: Device reported enroll progress, reported 2 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.873: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.873: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.873: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.873: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.874: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.875: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.875: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.875: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.875: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.875: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.875: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.875: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.875: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.876: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.876: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.876: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.876: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.876: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.876: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.877: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.877: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.877: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.877: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.877: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.877: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.878: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.878: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.878: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.878: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.878: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.878: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.878: Partial capture successful. Please touch the sensor again (3/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.878: Device reported enroll progress, reported 3 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.879: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.879: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.879: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.879: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.879: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.880: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.880: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.880: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.880: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.880: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.880: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.880: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.881: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.882: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.882: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.882: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.882: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.882: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.882: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.882: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.882: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.882: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.882: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.882: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.883: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.883: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.883: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.883: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.883: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.883: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.883: Partial capture successful. Please touch the sensor again (4/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.883: Device reported enroll progress, reported 4 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.883: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.883: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.883: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.883: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.884: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.885: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.885: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.885: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.885: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.885: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.885: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.885: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.885: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.886: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.886: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.886: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.886: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.886: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.886: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.886: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.886: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.886: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.886: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.886: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.886: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.887: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.888: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.888: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.888: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.888: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.888: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.888: Partial capture successful. Please touch the sensor again (5/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.888: Device reported enroll progress, reported 5 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.888: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.888: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.888: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.888: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.888: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.889: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.889: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.889: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.889: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.889: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.889: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.889: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.890: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.891: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.891: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.891: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.891: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.891: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.891: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.891: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.891: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.891: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.891: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.891: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.892: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.892: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.893: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.893: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.893: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.893: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.893: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.893: Partial capture successful. Please touch the sensor again (6/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.893: Device reported enroll progress, reported 6 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.893: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.893: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.893: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.893: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.894: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.894: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.894: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.894: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.894: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.894: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.894: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.894: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.895: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.896: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.896: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.896: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.896: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.896: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.896: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.896: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.896: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.896: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.896: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.896: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.897: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.897: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.897: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.898: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.898: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.898: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.898: Partial capture successful. Please touch the sensor again (7/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.898: Device reported enroll progress, reported 7 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.898: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.898: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.898: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.898: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.898: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.899: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.899: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.899: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.899: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.899: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.899: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.899: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.900: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.900: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.900: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.900: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.900: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.900: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.901: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.901: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.901: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.901: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.901: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.901: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.902: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.902: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.902: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.902: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.902: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.902: Response suffix valid: NO 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.902: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.902: Response suffix valid: yes 321s (process:2630): libfprint-device-DEBUG: 05:02:20.902: Device reported enroll progress, reported 7 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.902: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.902: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.902: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.902: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.903: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.904: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.904: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.904: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.904: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.904: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.904: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.904: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.905: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.905: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.905: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.905: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.905: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.905: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.905: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.906: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.906: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.906: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.906: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.906: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.906: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.907: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.907: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.907: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.907: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.907: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.907: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.907: Partial capture successful. Please touch the sensor again (8/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.907: Device reported enroll progress, reported 8 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.907: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.907: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.907: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.907: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.908: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.909: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.909: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.909: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.909: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.909: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.909: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.909: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.909: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.910: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.910: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.910: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.910: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.910: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.910: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.911: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.911: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.911: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.911: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.911: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.911: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.911: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.912: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.912: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.912: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.912: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.912: Response suffix valid: NO 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.912: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.912: Response suffix valid: yes 321s (process:2630): libfprint-device-DEBUG: 05:02:20.912: Device reported enroll progress, reported 8 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.912: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.912: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.912: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.912: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.913: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.914: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.914: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.914: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.914: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.914: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.914: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.914: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.915: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.916: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.916: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.916: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.916: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.916: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.916: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.916: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.917: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.917: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.917: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.917: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.917: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.917: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.918: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.918: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.918: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.918: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.918: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.918: Partial capture successful. Please touch the sensor again (9/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.918: Device reported enroll progress, reported 9 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.918: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.918: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.918: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.918: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.919: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.920: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.920: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.920: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.920: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.920: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.920: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.920: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.920: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.921: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.921: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.921: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.921: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.921: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.921: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.922: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.922: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.922: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.922: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.922: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.922: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.922: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.923: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.923: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.923: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.923: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.923: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.923: Partial capture successful. Please touch the sensor again (10/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.923: Device reported enroll progress, reported 10 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.923: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.923: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.923: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.923: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.924: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.925: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.925: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.925: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.925: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.925: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.925: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.925: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.925: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.926: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.926: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.926: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.926: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.926: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.926: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.927: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.927: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.927: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.927: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.927: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.927: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.927: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.928: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.928: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.928: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.928: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.928: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.928: Partial capture successful. Please touch the sensor again (11/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.928: Device reported enroll progress, reported 11 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.928: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.928: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.928: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.928: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.929: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.930: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.930: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.930: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.930: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.930: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.930: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.930: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.930: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.931: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.931: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.931: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.931: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.931: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.932: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.932: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.932: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.932: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.932: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.932: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.933: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.934: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.934: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.934: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.934: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.934: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.934: Partial capture successful. Please touch the sensor again (12/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.934: Device reported enroll progress, reported 12 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.934: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.934: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.934: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.934: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.934: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.935: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.935: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.935: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.935: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.935: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.935: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.935: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.936: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.936: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.936: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.936: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.936: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.936: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.936: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.937: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.937: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.937: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.937: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.937: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.937: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.938: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.938: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.938: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.938: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.938: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.938: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.938: Partial capture successful. Please touch the sensor again (13/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.938: Device reported enroll progress, reported 13 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.938: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.939: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.939: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.939: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.939: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.940: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.940: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.940: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.940: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.940: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.940: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.940: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.941: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.941: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.941: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.941: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.941: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.941: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.941: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.942: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.942: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.942: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.942: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.942: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.942: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.943: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.944: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.944: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.944: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.944: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.944: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.944: Partial capture successful. Please touch the sensor again (14/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.944: Device reported enroll progress, reported 14 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.944: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.944: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.944: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.944: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.944: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.945: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.945: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.945: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.945: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.945: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.945: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.945: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.946: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.947: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.947: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.947: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.947: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.947: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.947: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.948: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.948: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.948: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.948: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.948: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.948: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.948: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.949: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.949: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.949: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.949: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.949: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.949: Partial capture successful. Please touch the sensor again (15/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.949: Device reported enroll progress, reported 15 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.949: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.949: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.949: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.949: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.950: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.950: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.950: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.950: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.950: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.950: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.950: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.950: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.951: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.952: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.952: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.952: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.952: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.952: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.952: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.952: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.952: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.952: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.952: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.952: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.952: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.953: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.954: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.954: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.954: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.954: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.954: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.954: Partial capture successful. Please touch the sensor again (16/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.954: Device reported enroll progress, reported 16 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.954: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.954: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.954: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.954: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.954: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.955: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.955: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.955: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.955: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.955: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.955: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.955: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.956: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-device-DEBUG: 05:02:20.956: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.956: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.957: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.957: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.957: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.957: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.957: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.957: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.957: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.957: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.957: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.957: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.957: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.958: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.959: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.959: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.959: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.959: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.959: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.959: Partial capture successful. Please touch the sensor again (17/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.959: Device reported enroll progress, reported 17 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.959: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.959: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.959: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.959: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.959: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.960: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.960: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.960: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.960: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.960: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.960: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.960: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.961: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.961: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.961: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.961: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.961: [egismoc] ENROLL_STATES entering state 10 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.961: Wait for finger on sensor 321s (process:2630): libfprint-device-DEBUG: 05:02:20.961: Device reported finger status change: FP_FINGER_STATUS_NEEDED 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.962: Finger on sensor callback 321s (process:2630): libfprint-device-DEBUG: 05:02:20.962: Device reported finger status change: FP_FINGER_STATUS_PRESENT 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.962: [egismoc] ENROLL_STATES entering state 11 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.962: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.962: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.962: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.963: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.963: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.964: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.964: Read capture callback 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.964: Response prefix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.964: Response suffix valid: yes 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.964: Partial capture successful. Please touch the sensor again (18/20) 321s (process:2630): libfprint-device-DEBUG: 05:02:20.964: Device reported enroll progress, reported 18 of 20 have been completed 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.964: [egismoc] ENROLL_STATES entering state 8 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.964: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.964: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.964: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.964: [egismoc] CMD_STATES entering state 1 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.965: Command receive callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.965: [egismoc] CMD_STATES completed successfully 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.965: Task SSM next state callback 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.965: [egismoc] ENROLL_STATES entering state 9 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.965: Execute command and get response 321s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.965: Get check bytes 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.965: [egismoc] CMD_STATES entering state 0 321s (process:2630): libfprint-SSM-DEBUG: 05:02:20.966: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.966: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.966: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.966: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.966: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.967: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:20.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.967: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:20.967: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.967: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.967: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.967: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.967: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.968: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.969: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.969: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.969: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.969: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.969: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.969: Partial capture successful. Please touch the sensor again (19/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:20.969: Device reported enroll progress, reported 19 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.969: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.969: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.969: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.969: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.969: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.970: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.970: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.970: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.970: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.970: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.970: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.970: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.971: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.971: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.971: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.971: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.971: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.971: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:20.971: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.972: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:20.972: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.972: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.972: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.972: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.972: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.973: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.974: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.974: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.974: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.974: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.974: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.974: Partial capture successful. Please touch the sensor again (20/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:20.974: Device reported enroll progress, reported 20 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.974: [egismoc] ENROLL_STATES entering state 12 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.974: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.974: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.974: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.975: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.975: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.975: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.975: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.975: [egismoc] ENROLL_STATES entering state 13 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.975: New fingerprint ID: FP1-00000000-2-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.975: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.975: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.975: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.976: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.977: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.977: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.977: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.977: [egismoc] ENROLL_STATES entering state 14 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.977: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.977: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.977: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.978: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.979: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.979: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.979: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.979: [egismoc] ENROLL_STATES entering state 15 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.979: Enrollment was successful! 322s (process:2630): libfprint-device-DEBUG: 05:02:20.979: Device reported enroll completion 322s (process:2630): libfprint-device-DEBUG: 05:02:20.979: Device reported finger status change: FP_FINGER_STATUS_NONE 322s (process:2630): libfprint-device-DEBUG: 05:02:20.979: Print for finger FP_FINGER_LEFT_INDEX enrolled 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.979: [egismoc] ENROLL_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.979: Task SSM done 322s (process:2630): libfprint-device-DEBUG: 05:02:20.979: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 322s (process:2630): libfprint-device-DEBUG: 05:02:20.979: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.979: List 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.979: [egismoc] LIST_STATES entering state 0 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.979: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.979: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.979: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.980: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.981: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.981: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.981: List callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.981: Device fingerprint 1: FP1-00000000-2-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.981: Number of currently enrolled fingerprints on the device is 1 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.981: [egismoc] LIST_STATES entering state 1 322s (process:2630): libfprint-device-DEBUG: 05:02:20.981: Device reported listing completion 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.981: [egismoc] LIST_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.981: Task SSM done 322s (process:2630): libfprint-device-DEBUG: 05:02:20.981: Completing action FPI_DEVICE_ACTION_LIST in idle! 322s (process:2630): libfprint-device-DEBUG: 05:02:20.981: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-device-DEBUG: 05:02:20.981: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.981: Identify or Verify 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.981: [egismoc] IDENTIFY_STATES entering state 0 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.981: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.981: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.981: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.982: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.983: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.983: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.983: List callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.983: Device fingerprint 1: FP1-00000000-2-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.983: Number of currently enrolled fingerprints on the device is 1 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.983: [egismoc] IDENTIFY_STATES entering state 1 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.983: [egismoc] IDENTIFY_STATES entering state 2 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.983: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.983: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.983: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.983: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.984: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.984: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.984: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.984: [egismoc] IDENTIFY_STATES entering state 3 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.984: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.984: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.984: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.985: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.985: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.985: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.985: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.985: [egismoc] IDENTIFY_STATES entering state 4 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.985: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:20.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.986: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:20.986: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.986: [egismoc] IDENTIFY_STATES entering state 5 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.986: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.986: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.986: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.987: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.987: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.988: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.988: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.988: [egismoc] IDENTIFY_STATES entering state 6 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.988: Get check command 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.988: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.988: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.988: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.988: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.989: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.989: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.989: Identify check callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.989: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.989: Identify successful for: FP1-00000000-2-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.989: Verifying against: FP1-00000000-2-00000000-nobody 322s (process:2630): libfprint-device-DEBUG: 05:02:20.989: Device reported verify result 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.989: [egismoc] IDENTIFY_STATES entering state 7 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.989: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.989: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.989: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.989: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.990: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.990: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.990: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.990: [egismoc] IDENTIFY_STATES entering state 8 322s (process:2630): libfprint-device-DEBUG: 05:02:20.990: Device reported verify completion 322s (process:2630): libfprint-device-DEBUG: 05:02:20.990: Device reported finger status change: FP_FINGER_STATUS_NONE 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.990: [egismoc] IDENTIFY_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.990: Task SSM done 322s (process:2630): libfprint-device-DEBUG: 05:02:20.990: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 322s (process:2630): libfprint-device-DEBUG: 05:02:20.990: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-device-DEBUG: 05:02:20.991: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.991: Identify or Verify 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.991: [egismoc] IDENTIFY_STATES entering state 0 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.991: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.991: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.991: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.991: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.992: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.992: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.992: List callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.992: Device fingerprint 1: FP1-00000000-2-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.992: Number of currently enrolled fingerprints on the device is 1 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.992: [egismoc] IDENTIFY_STATES entering state 1 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.992: [egismoc] IDENTIFY_STATES entering state 2 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.992: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.992: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.992: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.993: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.993: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.993: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.993: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.993: [egismoc] IDENTIFY_STATES entering state 3 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.993: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.993: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.993: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.994: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.995: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.995: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.995: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.995: [egismoc] IDENTIFY_STATES entering state 4 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.995: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:20.995: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.995: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:20.996: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.996: [egismoc] IDENTIFY_STATES entering state 5 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.996: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.996: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.996: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.996: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.997: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.997: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.997: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.997: [egismoc] IDENTIFY_STATES entering state 6 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.997: Get check command 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.997: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.997: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.997: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.997: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.998: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.998: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.998: Identify check callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.998: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.998: Identify successful for: FP1-00000000-2-00000000-nobody 322s (process:2630): libfprint-device-DEBUG: 05:02:20.998: Device reported identify result 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.998: [egismoc] IDENTIFY_STATES entering state 7 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.998: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.998: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.998: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.999: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.999: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.999: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.999: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.999: [egismoc] IDENTIFY_STATES entering state 8 322s (process:2630): libfprint-device-DEBUG: 05:02:20.999: Device reported identify completion 322s (process:2630): libfprint-device-DEBUG: 05:02:20.999: Device reported finger status change: FP_FINGER_STATUS_NONE 322s (process:2630): libfprint-SSM-DEBUG: 05:02:20.999: [egismoc] IDENTIFY_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:20.999: Task SSM done 322s (process:2630): libfprint-device-DEBUG: 05:02:20.999: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 322s (process:2630): libfprint-device-DEBUG: 05:02:20.999: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-device-DEBUG: 05:02:21.000: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.000: Enroll 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.000: [egismoc] ENROLL_STATES entering state 0 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.000: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.000: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.000: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.001: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.001: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.001: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.001: List callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.001: Device fingerprint 1: FP1-00000000-2-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.001: Number of currently enrolled fingerprints on the device is 1 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.001: [egismoc] ENROLL_STATES entering state 1 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.001: [egismoc] ENROLL_STATES entering state 2 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.001: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.001: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.001: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.002: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.002: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.002: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.002: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.002: [egismoc] ENROLL_STATES entering state 3 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.002: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.002: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.002: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.003: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.004: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.004: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.004: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.004: [egismoc] ENROLL_STATES entering state 4 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.004: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.004: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.004: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.004: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.004: [egismoc] ENROLL_STATES entering state 5 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.004: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.004: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.004: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.005: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.005: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.005: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.005: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.005: [egismoc] ENROLL_STATES entering state 6 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.005: Get check command 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.005: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.005: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.005: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.006: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.007: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.007: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.007: Enroll check callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.007: Response suffix valid: NO 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.007: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.007: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.007: Task SSM done 322s (process:2630): libfprint-device-DEBUG: 05:02:21.007: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 322s (process:2630): libfprint-device-DEBUG: 05:02:21.007: Device reported enroll completion 322s (process:2630): libfprint-device-DEBUG: 05:02:21.007: Device reported finger status change: FP_FINGER_STATUS_NONE 322s (process:2630): libfprint-device-DEBUG: 05:02:21.007: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 322s (process:2630): libfprint-device-DEBUG: 05:02:21.007: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.007: List 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.007: [egismoc] LIST_STATES entering state 0 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.007: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.007: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.007: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.008: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.008: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.008: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.008: List callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.008: Device fingerprint 1: FP1-00000000-2-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.008: Number of currently enrolled fingerprints on the device is 1 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.008: [egismoc] LIST_STATES entering state 1 322s (process:2630): libfprint-device-DEBUG: 05:02:21.008: Device reported listing completion 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.008: [egismoc] LIST_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.008: Task SSM done 322s (process:2630): libfprint-device-DEBUG: 05:02:21.008: Completing action FPI_DEVICE_ACTION_LIST in idle! 322s (process:2630): libfprint-device-DEBUG: 05:02:21.008: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-device-DEBUG: 05:02:21.009: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.009: Enroll 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.009: [egismoc] ENROLL_STATES entering state 0 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.009: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.009: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.009: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.009: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.010: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.010: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.010: List callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.010: Device fingerprint 1: FP1-00000000-2-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.010: Number of currently enrolled fingerprints on the device is 1 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.010: [egismoc] ENROLL_STATES entering state 1 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.010: [egismoc] ENROLL_STATES entering state 2 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.010: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.010: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.010: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.010: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.011: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.011: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.011: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.011: [egismoc] ENROLL_STATES entering state 3 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.011: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.011: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.011: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.011: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.012: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.012: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.012: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.012: [egismoc] ENROLL_STATES entering state 4 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.012: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.012: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.013: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.013: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.013: [egismoc] ENROLL_STATES entering state 5 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.013: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.013: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.013: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.013: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.014: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.014: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.014: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.014: [egismoc] ENROLL_STATES entering state 6 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.014: Get check command 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.014: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.014: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.014: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.014: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.015: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.015: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.015: Enroll check callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.015: Response suffix valid: yes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.015: [egismoc] ENROLL_STATES entering state 7 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.015: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.015: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.015: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.015: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.016: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.016: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.016: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.016: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.016: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.016: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.016: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.016: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.017: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.017: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.017: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.017: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.017: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.017: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.017: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.017: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.018: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.018: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.018: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.018: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.018: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.018: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.019: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.019: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.019: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.019: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.019: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.019: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.019: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.020: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.020: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.020: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.020: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.020: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.020: Partial capture successful. Please touch the sensor again (1/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.020: Device reported enroll progress, reported 1 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.020: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.020: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.020: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.020: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.020: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.021: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.021: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.021: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.021: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.021: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.021: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.021: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.022: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.022: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.022: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.022: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.022: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.022: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.022: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.023: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.023: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.023: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.023: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.023: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.023: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.023: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.024: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.024: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.024: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.024: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.024: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.024: Partial capture successful. Please touch the sensor again (2/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.024: Device reported enroll progress, reported 2 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.024: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.024: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.024: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.024: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.025: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.026: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.026: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.026: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.026: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.026: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.026: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.026: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.026: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.027: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.027: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.027: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.027: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.027: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.027: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.027: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.027: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.027: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.027: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.027: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.027: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.028: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.028: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.029: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.029: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.029: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.029: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.029: Partial capture successful. Please touch the sensor again (3/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.029: Device reported enroll progress, reported 3 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.029: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.029: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.029: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.029: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.029: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.030: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.030: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.030: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.030: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.030: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.030: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.030: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.030: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.031: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.031: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.031: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.031: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.031: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.031: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.032: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.032: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.032: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.032: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.032: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.032: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.032: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.033: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.033: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.033: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.033: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.033: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.033: Partial capture successful. Please touch the sensor again (4/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.033: Device reported enroll progress, reported 4 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.033: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.033: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.033: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.033: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.034: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.034: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.034: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.035: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.035: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.035: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.035: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.035: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.035: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.036: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.036: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.036: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.036: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.036: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.036: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.036: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.036: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.036: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.036: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.036: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.036: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.037: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.038: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.038: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.038: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.038: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.038: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.038: Partial capture successful. Please touch the sensor again (5/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.038: Device reported enroll progress, reported 5 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.038: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.038: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.038: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.038: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.038: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.039: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.039: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.039: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.039: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.039: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.039: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.039: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.040: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.040: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.040: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.040: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.040: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.040: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.040: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.041: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.041: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.041: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.041: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.041: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.041: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.042: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.042: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.042: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.042: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.042: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.042: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.042: Partial capture successful. Please touch the sensor again (6/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.042: Device reported enroll progress, reported 6 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.042: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.042: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.042: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.042: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.043: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.043: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.043: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.043: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.044: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.044: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.044: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.044: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.044: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.045: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.045: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.045: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.045: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.045: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.045: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.045: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.045: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.045: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.045: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.045: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.045: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.046: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.046: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.046: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.046: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.046: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.046: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.046: Partial capture successful. Please touch the sensor again (7/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.046: Device reported enroll progress, reported 7 of 20 have been completed 322s listing - device should have prints 322s clear device storage 322s clear done 322s listing - device should be empty 322s enrolling 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 1, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 2, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 3, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 4, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 5, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 6, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 7, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 8, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 9, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 10, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 11, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 12, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 13, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 14, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 15, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 16, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 17, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 18, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 19, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 20, , None, None) 322s enroll done 322s listing - device should have 1 print 322s verifying 322s verify done 322s async identifying 322s indentification_done: 322s try to enroll duplicate 322s duplicate enroll attempt done 322s listing - device should still only have 1 print 322s enroll new finger 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 1, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 2, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 3, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 4, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 5, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 6, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 7, , None, None)(process:2630): libfprint-SSM-DEBUG: 05:02:21.046: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.046: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.046: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.046: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.047: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.048: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.048: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.048: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.048: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.048: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.048: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.048: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.048: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.049: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.049: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.049: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.049: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.049: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.049: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.050: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.050: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.050: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.050: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.050: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.050: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.050: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.051: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.051: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.051: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.051: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.051: Response suffix valid: NO 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.051: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.051: Response suffix valid: yes 322s (process:2630): libfprint-device-DEBUG: 05:02:21.051: Device reported enroll progress, reported 7 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.051: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.051: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.051: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.051: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.052: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.053: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.053: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.053: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.053: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.053: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.053: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.053: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.053: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.054: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.054: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.054: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.054: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.054: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.054: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.054: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.054: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.054: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.054: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.054: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.054: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.055: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.056: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.056: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.056: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.056: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.056: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.056: Partial capture successful. Please touch the sensor again (8/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.056: Device reported enroll progress, reported 8 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.056: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.056: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.056: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.056: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.056: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.057: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.057: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.057: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.057: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.057: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.057: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.057: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.057: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.058: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.058: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.058: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.058: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.058: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.058: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.059: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.059: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.059: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.059: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.059: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.059: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.059: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.060: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.060: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.060: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.060: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.060: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.060: Partial capture successful. Please touch the sensor again (9/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.060: Device reported enroll progress, reported 9 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.060: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.060: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.060: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.060: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.061: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.062: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.062: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.062: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.062: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.062: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.062: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.062: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.062: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.063: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.063: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.063: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.063: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.063: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.063: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.063: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.063: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.063: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.063: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.063: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.063: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.064: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.065: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.065: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.065: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.065: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.065: Response suffix valid: NO 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.065: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.065: Response suffix valid: yes 322s (process:2630): libfprint-device-DEBUG: 05:02:21.065: Device reported enroll progress, reported 9 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.065: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.065: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.065: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.065: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.065: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.066: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.066: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.066: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.066: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.066: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.066: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.066: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.067: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.067: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.067: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.067: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.067: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.067: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.068: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.068: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.068: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.068: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.068: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.068: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.068: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.069: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.069: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.069: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.069: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.069: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.069: Partial capture successful. Please touch the sensor again (10/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.069: Device reported enroll progress, reported 10 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.069: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.069: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.069: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.069: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.070: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.070: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.070: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.070: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.070: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.070: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.070: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.070: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.071: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.071: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.071: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.072: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.072: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.072: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.072: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.072: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.072: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.072: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.072: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.072: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.072: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.073: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.073: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.073: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.073: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.073: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.073: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.073: Partial capture successful. Please touch the sensor again (11/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.073: Device reported enroll progress, reported 11 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.074: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.074: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.074: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.074: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.074: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.075: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.075: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.075: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.075: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.075: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.075: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.075: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.075: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.076: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.076: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.076: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.076: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.076: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.076: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.077: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.077: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.077: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.077: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.077: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.077: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.077: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.078: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.078: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.078: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.078: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.078: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.078: Partial capture successful. Please touch the sensor again (12/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.078: Device reported enroll progress, reported 12 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.078: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.078: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.078: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.078: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.079: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.079: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.079: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.079: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.079: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.079: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.079: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.079: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.080: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.081: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.081: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.081: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.081: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.081: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.081: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.081: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.081: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.081: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.081: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.081: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.081: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.082: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.083: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.083: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.083: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.083: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.083: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.083: Partial capture successful. Please touch the sensor again (13/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.083: Device reported enroll progress, reported 13 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.083: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.083: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.083: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.083: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.084: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.085: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.085: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.085: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.085: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.085: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.085: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.085: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.086: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.086: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.086: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.086: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.086: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.086: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.086: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.087: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.087: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.087: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.087: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.087: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.087: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.088: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.089: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.089: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.089: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.089: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.089: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.089: Partial capture successful. Please touch the sensor again (14/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.089: Device reported enroll progress, reported 14 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.089: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.089: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.089: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.089: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.090: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.090: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.090: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.091: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.091: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.091: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.091: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.091: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.091: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.092: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.092: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.092: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.092: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.092: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.092: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.092: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.092: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.092: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.092: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.092: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.092: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.093: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.094: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.094: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.094: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.094: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.094: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.094: Partial capture successful. Please touch the sensor again (15/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.094: Device reported enroll progress, reported 15 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.094: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.094: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.094: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.094: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.094: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.095: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.095: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.095: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.095: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.095: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.095: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.095: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.096: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.096: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.096: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.096: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.096: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.096: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.096: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.097: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.097: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.097: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.097: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.097: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.097: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.097: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.098: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.098: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.098: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.098: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.098: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.098: Partial capture successful. Please touch the sensor again (16/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.098: Device reported enroll progress, reported 16 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.098: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.098: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.098: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.098: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.099: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.099: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.100: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.100: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.100: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.100: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.100: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.100: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.100: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.101: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.101: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.101: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.101: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.101: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.101: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.101: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.101: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.101: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.101: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.101: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.101: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.102: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.102: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.102: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.102: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.102: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.102: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.102: Partial capture successful. Please touch the sensor again (17/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.102: Device reported enroll progress, reported 17 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.102: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.102: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.102: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.102: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.103: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.104: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.104: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.104: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.104: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.104: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.104: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.104: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.104: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.105: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.105: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.105: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.105: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.105: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.105: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.106: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.106: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.106: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.106: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.106: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.106: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.106: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.107: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.107: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.107: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.107: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.107: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.107: Partial capture successful. Please touch the sensor again (18/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.107: Device reported enroll progress, reported 18 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.107: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.107: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.107: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.107: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.108: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.108: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.108: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.108: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.108: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.108: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.108: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.108: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.109: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.110: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.110: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.110: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.110: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.110: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.110: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.110: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.110: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.110: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.110: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.110: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.110: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.111: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.111: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.111: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.111: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.111: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.111: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.111: Partial capture successful. Please touch the sensor again (19/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.111: Device reported enroll progress, reported 19 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.111: [egismoc] ENROLL_STATES entering state 8 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.111: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.111: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.112: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.112: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.113: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.113: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.113: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.113: [egismoc] ENROLL_STATES entering state 9 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.113: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.113: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.113: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.113: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.114: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.114: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.114: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.114: [egismoc] ENROLL_STATES entering state 10 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.114: Wait for finger on sensor 322s (process:2630): libfprint-device-DEBUG: 05:02:21.114: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.115: Finger on sensor callback 322s (process:2630): libfprint-device-DEBUG: 05:02:21.115: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.115: [egismoc] ENROLL_STATES entering state 11 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.115: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.115: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.115: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.115: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.116: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.116: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.116: Read capture callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.116: Response prefix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.116: Response suffix valid: yes 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.116: Partial capture successful. Please touch the sensor again (20/20) 322s (process:2630): libfprint-device-DEBUG: 05:02:21.116: Device reported enroll progress, reported 20 of 20 have been completed 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.116: [egismoc] ENROLL_STATES entering state 12 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.116: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.116: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.116: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.117: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.117: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.117: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.117: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.117: [egismoc] ENROLL_STATES entering state 13 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.117: New fingerprint ID: FP1-00000000-7-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.117: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.117: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.117: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.118: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.118: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.118: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.119: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.119: [egismoc] ENROLL_STATES entering state 14 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.119: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.119: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.119: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.119: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.120: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.120: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.120: Task SSM next state callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.120: [egismoc] ENROLL_STATES entering state 15 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.120: Enrollment was successful! 322s (process:2630): libfprint-device-DEBUG: 05:02:21.120: Device reported enroll completion 322s (process:2630): libfprint-device-DEBUG: 05:02:21.120: Device reported finger status change: FP_FINGER_STATUS_NONE 322s (process:2630): libfprint-device-DEBUG: 05:02:21.120: Print for finger FP_FINGER_RIGHT_INDEX enrolled 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.120: [egismoc] ENROLL_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.120: Task SSM done 322s (process:2630): libfprint-device-DEBUG: 05:02:21.120: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 322s (process:2630): libfprint-device-DEBUG: 05:02:21.120: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.120: List 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.120: [egismoc] LIST_STATES entering state 0 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.120: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.120: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.120: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.121: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.121: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.121: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.121: List callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.121: Device fingerprint 1: FP1-00000000-2-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.121: Device fingerprint 2: FP1-00000000-7-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.121: Number of currently enrolled fingerprints on the device is 2 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.121: [egismoc] LIST_STATES entering state 1 322s (process:2630): libfprint-device-DEBUG: 05:02:21.121: Device reported listing completion 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.121: [egismoc] LIST_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.121: Task SSM done 322s (process:2630): libfprint-device-DEBUG: 05:02:21.121: Completing action FPI_DEVICE_ACTION_LIST in idle! 322s (process:2630): libfprint-device-DEBUG: 05:02:21.121: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.122: Delete 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.122: [egismoc] DELETE_STATES entering state 0 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.122: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.122: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.122: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.122: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.123: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.123: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.123: List callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.123: Device fingerprint 1: FP1-00000000-2-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.123: Device fingerprint 2: FP1-00000000-7-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.123: Number of currently enrolled fingerprints on the device is 2 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.123: [egismoc] DELETE_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.123: Get delete command 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.123: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.123: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.123: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.123: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.123: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.124: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.124: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.124: Delete callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.124: Response prefix valid: yes 322s (process:2630): libfprint-device-DEBUG: 05:02:21.124: Device reported deletion completion 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.124: [egismoc] DELETE_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.124: Task SSM done 322s (process:2630): libfprint-device-DEBUG: 05:02:21.124: Completing action FPI_DEVICE_ACTION_DELETE in idle! 322s (process:2630): libfprint-device-DEBUG: 05:02:21.124: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.124: List 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.124: [egismoc] LIST_STATES entering state 0 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.124: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.124: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.124: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.125: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.125: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.125: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.125: List callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.125: Device fingerprint 1: FP1-00000000-7-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.125: Number of currently enrolled fingerprints on the device is 1 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.125: [egismoc] LIST_STATES entering state 1 322s (process:2630): libfprint-device-DEBUG: 05:02:21.126: Device reported listing completion 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.126: [egismoc] LIST_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.126: Task SSM done 322s (process:2630): libfprint-device-DEBUG: 05:02:21.126: Completing action FPI_DEVICE_ACTION_LIST in idle! 322s (process:2630): libfprint-device-DEBUG: 05:02:21.126: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.126: Clear storage 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.126: [egismoc] DELETE_STATES entering state 0 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.126: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.126: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.126: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.126: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.127: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.127: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.127: List callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.127: Device fingerprint 1: FP1-00000000-7-00000000-nobody 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.127: Number of currently enrolled fingerprints on the device is 1 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.127: [egismoc] DELETE_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.127: Get delete command 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.127: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.127: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.127: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.128: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.128: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.128: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.128: Delete callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.128: Response prefix valid: yes 322s (process:2630): libfprint-device-DEBUG: 05:02:21.128: Device reported deletion completion 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.128: [egismoc] DELETE_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.128: Task SSM done 322s (process:2630): libfprint-device-DEBUG: 05:02:21.128: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 322s (process:2630): libfprint-device-DEBUG: 05:02:21.128: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.128: List 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.128: [egismoc] LIST_STATES entering state 0 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.128: Execute command and get response 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.128: Get check bytes 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.128: [egismoc] CMD_STATES entering state 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.129: [egismoc] CMD_STATES entering state 1 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.130: Command receive callback 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.130: [egismoc] CMD_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.130: List callback 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.130: Number of currently enrolled fingerprints on the device is 0 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.130: [egismoc] LIST_STATES entering state 1 322s (process:2630): libfprint-device-DEBUG: 05:02:21.130: Device reported listing completion 322s (process:2630): libfprint-SSM-DEBUG: 05:02:21.130: [egismoc] LIST_STATES completed successfully 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.130: Task SSM done 322s (process:2630): libfprint-device-DEBUG: 05:02:21.130: Completing action FPI_DEVICE_ACTION_LIST in idle! 322s (process:2630): libfprint-device-DEBUG: 05:02:21.130: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.130: Closing device 322s (process:2630): libfprint-egismoc-DEBUG: 05:02:21.130: Cancel 322s (process:2630): libfprint-device-DEBUG: 05:02:21.130: Device reported close completion 322s (process:2630): libfprint-device-DEBUG: 05:02:21.131: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 322s (process:2630): libfprint-device-DEBUG: 05:02:21.131: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 8, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 9, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 10, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 11, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 12, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 13, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 14, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 15, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 16, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 17, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 18, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 19, , None, None) 322s finger status: 322s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xf14c8843e680 (FpiDeviceEgisMoc at 0x1912ba90)>, 20, , None, None) 322s enroll new finger done 322s listing - device should have 2 prints 322s deleting first print 322s delete done 322s listing - device should only have second print 322s clear device storage 322s clear done 322s listing - device should be empty 322s ** (umockdev-run:2626): DEBUG: 05:02:21.165: umockdev.vala:154: Removing test bed /tmp/umockdev.DWU412 322s (umockdev-run:2626): GLib-DEBUG: 05:02:21.169: unsetenv() is not thread-safe and should not be used after threads are created 322s PASS: libfprint-2/driver-egismoc-0586.test 322s Running test: libfprint-2/virtual-image.test 322s (process:2636): libfprint-context-DEBUG: 05:02:21.311: Initializing FpContext (libfprint version 1.94.9+tod1) 322s (process:2636): libfprint-tod-DEBUG: 05:02:21.311: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 322s (process:2636): libfprint-context-DEBUG: 05:02:21.314: No driver found for USB device 1D6B:0003 322s (process:2636): libfprint-context-DEBUG: 05:02:21.314: No driver found for USB device 0627:0001 322s (process:2636): libfprint-context-DEBUG: 05:02:21.314: No driver found for USB device 1D6B:0002 322s (process:2636): libfprint-context-DEBUG: 05:02:21.314: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-7xsjisdv/virtual-image.socket 322s (process:2636): libfprint-context-DEBUG: 05:02:21.315: created 322s (process:2636): libfprint-device-DEBUG: 05:02:21.315: Device reported probe completion 322s (process:2636): libfprint-device-DEBUG: 05:02:21.316: Completing action FPI_DEVICE_ACTION_PROBE in idle! 322s (process:2636): libfprint-device-DEBUG: 05:02:21.316: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 322s test_capture_prevents_close (__main__.VirtualImage.test_capture_prevents_close) ... (process:2636): libfprint-virtual_image-DEBUG: 05:02:21.322: 99240248: ../libfprint/drivers/virtual-image.c:216 322s (process:2636): libfprint-virtual_device_connection-DEBUG: 05:02:21.322: 99240348: ../libfprint/drivers/virtual-device-listener.c:153 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.422: Image device open completed 322s (process:2636): libfprint-device-DEBUG: 05:02:21.422: Device reported open completion 322s (process:2636): libfprint-device-DEBUG: 05:02:21.422: Completing action FPI_DEVICE_ACTION_OPEN in idle! 322s (process:2636): libfprint-device-DEBUG: 05:02:21.422: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 322s (process:2636): libfprint-device-DEBUG: 05:02:21.423: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.423: Activating image device 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.423: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.423: Image device activation completed 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.423: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.423: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 322s (process:2636): libfprint-device-DEBUG: 05:02:21.423: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2636): libfprint-virtual_device_connection-DEBUG: 05:02:21.423: Got a new connection! 322s (process:2636): libfprint-device-DEBUG: 05:02:21.424: Idle cancelling on ongoing operation! 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.424: Deactivating image device 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.424: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.424: Image device deactivation completed 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.424: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 322s (process:2636): libfprint-device-DEBUG: 05:02:21.424: Device reported generic error (Operation was cancelled) during action; action was: FPI_DEVICE_ACTION_CAPTURE 322s (process:2636): libfprint-device-DEBUG: 05:02:21.424: Device reported capture completion 322s (process:2636): libfprint-device-DEBUG: 05:02:21.424: Device reported finger status change: FP_FINGER_STATUS_NONE 322s (process:2636): libfprint-device-DEBUG: 05:02:21.424: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 322s (process:2636): libfprint-device-DEBUG: 05:02:21.424: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 322s (process:2636): libfprint-virtual_image-DEBUG: 05:02:21.425: 99343517: ../libfprint/drivers/virtual-image.c:244 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.525: Image device close completed 322s (process:2636): libfprint-device-DEBUG: 05:02:21.525: Device reported close completion 322s (process:2636): libfprint-device-DEBUG: 05:02:21.525: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 322s (process:2636): libfprint-device-DEBUG: 05:02:21.525: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 322s Capture operation finished 322s Capture cancelled as expected 322s ok 322s test_enroll_verify (__main__.VirtualImage.test_enroll_verify) ... (process:2636): libfprint-virtual_image-DEBUG: 05:02:21.526: 99444209: ../libfprint/drivers/virtual-image.c:216 322s (process:2636): libfprint-virtual_device_connection-DEBUG: 05:02:21.526: 99444236: ../libfprint/drivers/virtual-device-listener.c:153 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.625: Image device open completed 322s (process:2636): libfprint-device-DEBUG: 05:02:21.625: Device reported open completion 322s (process:2636): libfprint-device-DEBUG: 05:02:21.626: Completing action FPI_DEVICE_ACTION_OPEN in idle! 322s (process:2636): libfprint-device-DEBUG: 05:02:21.626: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 322s (process:2636): libfprint-device-DEBUG: 05:02:21.627: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.627: Activating image device 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.627: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.627: Image device activation completed 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.627: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.627: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 322s (process:2636): libfprint-device-DEBUG: 05:02:21.627: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2636): libfprint-virtual_device_connection-DEBUG: 05:02:21.628: Got a new connection! 322s (process:2636): libfprint-virtual_image-DEBUG: 05:02:21.628: image data: 0x1da75ed0 322s (process:2636): libfprint-device-DEBUG: 05:02:21.628: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.628: Image device reported finger status: on 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.628: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.628: Image device captured an image 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.628: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 322s (process:2636): libfprint-device-DEBUG: 05:02:21.628: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2636): libfprint-device-DEBUG: 05:02:21.628: Device reported finger status change: FP_FINGER_STATUS_NONE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.628: Image device reported finger status: off 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.628: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 322s (process:2636): libfprint-image-DEBUG: 05:02:21.652: Minutiae scan completed in 0.023723 secs 322s (process:2636): libfprint-device-DEBUG: 05:02:21.652: Device reported enroll progress, reported 1 of 5 have been completed 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.652: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 322s (process:2636): libfprint-device-DEBUG: 05:02:21.652: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2636): libfprint-device-DEBUG: 05:02:21.652: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.652: Image device reported finger status: on 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.652: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 322s (process:2636): libfprint-virtual_image-DEBUG: 05:02:21.653: image data: 0x1da75ed0 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.653: Image device captured an image 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.653: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 322s (process:2636): libfprint-device-DEBUG: 05:02:21.653: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2636): libfprint-image-DEBUG: 05:02:21.676: Minutiae scan completed in 0.023414 secs 322s (process:2636): libfprint-device-DEBUG: 05:02:21.676: Device reported enroll progress, reported 2 of 5 have been completed 322s (process:2636): libfprint-device-DEBUG: 05:02:21.677: Device reported finger status change: FP_FINGER_STATUS_NONE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.677: Image device reported finger status: off 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.677: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.677: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 322s (process:2636): libfprint-device-DEBUG: 05:02:21.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2636): libfprint-virtual_image-DEBUG: 05:02:21.677: image data: 0x1da76840 322s (process:2636): libfprint-device-DEBUG: 05:02:21.677: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.677: Image device reported finger status: on 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.678: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.678: Image device captured an image 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.678: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 322s (process:2636): libfprint-device-DEBUG: 05:02:21.678: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2636): libfprint-device-DEBUG: 05:02:21.678: Device reported finger status change: FP_FINGER_STATUS_NONE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.678: Image device reported finger status: off 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.678: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 322s (process:2636): libfprint-image-DEBUG: 05:02:21.701: Minutiae scan completed in 0.023478 secs 322s (process:2636): libfprint-device-DEBUG: 05:02:21.701: Device reported enroll progress, reported 3 of 5 have been completed 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.701: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 322s (process:2636): libfprint-device-DEBUG: 05:02:21.702: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2636): libfprint-virtual_image-DEBUG: 05:02:21.702: image data: 0x1da771b0 322s (process:2636): libfprint-device-DEBUG: 05:02:21.702: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.702: Image device reported finger status: on 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.702: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.702: Image device captured an image 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.702: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 322s (process:2636): libfprint-device-DEBUG: 05:02:21.702: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2636): libfprint-device-DEBUG: 05:02:21.702: Device reported finger status change: FP_FINGER_STATUS_NONE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.702: Image device reported finger status: off 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.702: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 322s (process:2636): libfprint-image-DEBUG: 05:02:21.726: Minutiae scan completed in 0.023587 secs 322s (process:2636): libfprint-device-DEBUG: 05:02:21.726: Device reported enroll progress, reported 4 of 5 have been completed 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.726: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 322s (process:2636): libfprint-device-DEBUG: 05:02:21.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2636): libfprint-virtual_image-DEBUG: 05:02:21.726: image data: 0x1da77b20 322s (process:2636): libfprint-device-DEBUG: 05:02:21.726: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.726: Image device reported finger status: on 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.726: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.726: Image device captured an image 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.726: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 322s (process:2636): libfprint-device-DEBUG: 05:02:21.726: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2636): libfprint-device-DEBUG: 05:02:21.726: Device reported finger status change: FP_FINGER_STATUS_NONE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.726: Image device reported finger status: off 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.726: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 322s (process:2636): libfprint-image-DEBUG: 05:02:21.750: Minutiae scan completed in 0.023390 secs 322s (process:2636): libfprint-device-DEBUG: 05:02:21.750: Device reported enroll progress, reported 5 of 5 have been completed 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.750: Deactivating image device 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.750: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.750: Image device deactivation completed 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.750: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 322s (process:2636): libfprint-device-DEBUG: 05:02:21.750: Device reported enroll completion 322s (process:2636): libfprint-device-DEBUG: 05:02:21.750: Print for finger FP_FINGER_LEFT_THUMB enrolled 322s (process:2636): libfprint-device-DEBUG: 05:02:21.750: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 322s (process:2636): libfprint-device-DEBUG: 05:02:21.750: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 322s (process:2636): libfprint-device-DEBUG: 05:02:21.751: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Activating image device 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Image device activation completed 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 322s (process:2636): libfprint-device-DEBUG: 05:02:21.751: Device reported finger status change: FP_FINGER_STATUS_NEEDED 322s (process:2636): libfprint-virtual_image-DEBUG: 05:02:21.751: image data: 0x1da7b4e0 322s (process:2636): libfprint-device-DEBUG: 05:02:21.751: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Image device reported finger status: on 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Image device captured an image 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 322s (process:2636): libfprint-device-DEBUG: 05:02:21.751: Device reported finger status change: FP_FINGER_STATUS_PRESENT 322s (process:2636): libfprint-device-DEBUG: 05:02:21.751: Device reported finger status change: FP_FINGER_STATUS_NONE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Image device reported finger status: off 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Deactivating image device 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Image device deactivation completed 322s (process:2636): libfprint-image_device-DEBUG: 05:02:21.751: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 322s (process:2636): libfprint-image-DEBUG: 05:02:21.775: Minutiae scan completed in 0.023597 secs 323s (process:2636): libfprint-print-DEBUG: 05:02:22.743: score 1093/40 323s (process:2636): libfprint-device-DEBUG: 05:02:22.744: Device reported verify result 323s (process:2636): libfprint-device-DEBUG: 05:02:22.744: Device reported verify completion 323s (process:2636): libfprint-device-DEBUG: 05:02:22.744: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 323s (process:2636): libfprint-device-DEBUG: 05:02:22.744: Updated temperature model after 0.99 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 323s (process:2636): libfprint-device-DEBUG: 05:02:22.744: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Activating image device 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Image device activation completed 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 323s (process:2636): libfprint-device-DEBUG: 05:02:22.744: Device reported finger status change: FP_FINGER_STATUS_NEEDED 323s (process:2636): libfprint-virtual_image-DEBUG: 05:02:22.744: image data: 0x1da8a1b0 323s (process:2636): libfprint-device-DEBUG: 05:02:22.744: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Image device reported finger status: on 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Image device captured an image 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 323s (process:2636): libfprint-device-DEBUG: 05:02:22.744: Device reported finger status change: FP_FINGER_STATUS_PRESENT 323s (process:2636): libfprint-device-DEBUG: 05:02:22.744: Device reported finger status change: FP_FINGER_STATUS_NONE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Image device reported finger status: off 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Deactivating image device 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Image device deactivation completed 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.744: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 323s (process:2636): libfprint-image-DEBUG: 05:02:22.766: Minutiae scan completed in 0.021262 secs 323s (process:2636): libfprint-print-DEBUG: 05:02:22.772: score 10/40 323s (process:2636): libfprint-print-DEBUG: 05:02:22.778: score 10/40 323s (process:2636): libfprint-print-DEBUG: 05:02:22.784: score 10/40 323s (process:2636): libfprint-print-DEBUG: 05:02:22.790: score 10/40 323s (process:2636): libfprint-print-DEBUG: 05:02:22.795: score 10/40 323s (process:2636): libfprint-device-DEBUG: 05:02:22.795: Device reported verify result 323s (process:2636): libfprint-device-DEBUG: 05:02:22.795: Device reported verify completion 323s (process:2636): libfprint-device-DEBUG: 05:02:22.796: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 323s (process:2636): libfprint-device-DEBUG: 05:02:22.796: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 323s (process:2636): libfprint-device-DEBUG: 05:02:22.796: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.796: Activating image device 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.796: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.796: Image device activation completed 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.796: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.796: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 323s (process:2636): libfprint-device-DEBUG: 05:02:22.796: Device reported finger status change: FP_FINGER_STATUS_NEEDED 323s (process:2636): libfprint-virtual_image-DEBUG: 05:02:22.797: image data: 0x1da991c0 323s (process:2636): libfprint-device-DEBUG: 05:02:22.797: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.797: Image device reported finger status: on 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.797: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.797: Image device captured an image 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.797: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 323s (process:2636): libfprint-device-DEBUG: 05:02:22.797: Device reported finger status change: FP_FINGER_STATUS_PRESENT 323s (process:2636): libfprint-device-DEBUG: 05:02:22.797: Device reported finger status change: FP_FINGER_STATUS_NONE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.797: Image device reported finger status: off 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.797: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 323s (process:2636): libfprint-image-DEBUG: 05:02:22.819: Minutiae scan completed in 0.021435 secs 323s (process:2636): libfprint-device-DEBUG: 05:02:22.819: Device reported enroll progress, reported 1 of 5 have been completed 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.820: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 323s (process:2636): libfprint-device-DEBUG: 05:02:22.820: Device reported finger status change: FP_FINGER_STATUS_NEEDED 323s (process:2636): libfprint-device-DEBUG: 05:02:22.821: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.821: Image device reported finger status: on 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.821: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 323s (process:2636): libfprint-virtual_image-DEBUG: 05:02:22.821: image data: 0x1da991c0 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.821: Image device captured an image 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.821: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 323s (process:2636): libfprint-device-DEBUG: 05:02:22.821: Device reported finger status change: FP_FINGER_STATUS_PRESENT 323s (process:2636): libfprint-image-DEBUG: 05:02:22.842: Minutiae scan completed in 0.021046 secs 323s (process:2636): libfprint-device-DEBUG: 05:02:22.843: Device reported enroll progress, reported 2 of 5 have been completed 323s (process:2636): libfprint-device-DEBUG: 05:02:22.844: Device reported finger status change: FP_FINGER_STATUS_NONE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.844: Image device reported finger status: off 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.844: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.844: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 323s (process:2636): libfprint-device-DEBUG: 05:02:22.844: Device reported finger status change: FP_FINGER_STATUS_NEEDED 323s (process:2636): libfprint-virtual_image-DEBUG: 05:02:22.845: image data: 0x1da991c0 323s (process:2636): libfprint-device-DEBUG: 05:02:22.846: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.846: Image device reported finger status: on 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.846: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.846: Image device captured an image 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.846: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 323s (process:2636): libfprint-device-DEBUG: 05:02:22.846: Device reported finger status change: FP_FINGER_STATUS_PRESENT 323s (process:2636): libfprint-device-DEBUG: 05:02:22.846: Device reported finger status change: FP_FINGER_STATUS_NONE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.846: Image device reported finger status: off 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.846: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 323s (process:2636): libfprint-image-DEBUG: 05:02:22.867: Minutiae scan completed in 0.021418 secs 323s (process:2636): libfprint-device-DEBUG: 05:02:22.868: Device reported enroll progress, reported 3 of 5 have been completed 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.868: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 323s (process:2636): libfprint-device-DEBUG: 05:02:22.868: Device reported finger status change: FP_FINGER_STATUS_NEEDED 323s (process:2636): libfprint-virtual_image-DEBUG: 05:02:22.869: image data: 0x1da991c0 323s (process:2636): libfprint-device-DEBUG: 05:02:22.869: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.869: Image device reported finger status: on 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.869: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.869: Image device captured an image 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.869: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 323s (process:2636): libfprint-device-DEBUG: 05:02:22.869: Device reported finger status change: FP_FINGER_STATUS_PRESENT 323s (process:2636): libfprint-device-DEBUG: 05:02:22.869: Device reported finger status change: FP_FINGER_STATUS_NONE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.869: Image device reported finger status: off 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.869: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 323s (process:2636): libfprint-image-DEBUG: 05:02:22.892: Minutiae scan completed in 0.022510 secs 323s (process:2636): libfprint-device-DEBUG: 05:02:22.892: Device reported enroll progress, reported 4 of 5 have been completed 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.892: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 323s (process:2636): libfprint-device-DEBUG: 05:02:22.892: Device reported finger status change: FP_FINGER_STATUS_NEEDED 323s (process:2636): libfprint-virtual_image-DEBUG: 05:02:22.893: image data: 0x1da991c0 323s (process:2636): libfprint-device-DEBUG: 05:02:22.893: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.893: Image device reported finger status: on 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.893: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.893: Image device captured an image 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.893: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 323s (process:2636): libfprint-device-DEBUG: 05:02:22.893: Device reported finger status change: FP_FINGER_STATUS_PRESENT 323s (process:2636): libfprint-device-DEBUG: 05:02:22.893: Device reported finger status change: FP_FINGER_STATUS_NONE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.893: Image device reported finger status: off 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.893: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 323s (process:2636): libfprint-image-DEBUG: 05:02:22.915: Minutiae scan completed in 0.021317 secs 323s (process:2636): libfprint-device-DEBUG: 05:02:22.915: Device reported enroll progress, reported 5 of 5 have been completed 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.916: Deactivating image device 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.916: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.916: Image device deactivation completed 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.916: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 323s (process:2636): libfprint-device-DEBUG: 05:02:22.916: Device reported enroll completion 323s (process:2636): libfprint-device-DEBUG: 05:02:22.916: Print for finger FP_FINGER_LEFT_THUMB enrolled 323s (process:2636): libfprint-device-DEBUG: 05:02:22.916: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 323s (process:2636): libfprint-device-DEBUG: 05:02:22.916: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 323s (process:2636): libfprint-device-DEBUG: 05:02:22.917: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.917: Activating image device 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.917: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.917: Image device activation completed 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.917: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.917: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 323s (process:2636): libfprint-device-DEBUG: 05:02:22.917: Device reported finger status change: FP_FINGER_STATUS_NEEDED 323s (process:2636): libfprint-virtual_image-DEBUG: 05:02:22.918: image data: 0x1da8a1b0 323s (process:2636): libfprint-device-DEBUG: 05:02:22.918: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.919: Image device reported finger status: on 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.919: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.919: Image device captured an image 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.919: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 323s (process:2636): libfprint-device-DEBUG: 05:02:22.919: Device reported finger status change: FP_FINGER_STATUS_PRESENT 323s (process:2636): libfprint-device-DEBUG: 05:02:22.919: Device reported finger status change: FP_FINGER_STATUS_NONE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.919: Image device reported finger status: off 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.919: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.919: Deactivating image device 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.919: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.919: Image device deactivation completed 323s (process:2636): libfprint-image_device-DEBUG: 05:02:22.919: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 323s (process:2636): libfprint-image-DEBUG: 05:02:22.943: Minutiae scan completed in 0.023706 secs 324s (process:2636): libfprint-print-DEBUG: 05:02:23.910: score 1093/40 324s (process:2636): libfprint-device-DEBUG: 05:02:23.910: Device reported verify result 324s (process:2636): libfprint-device-DEBUG: 05:02:23.910: Device reported verify completion 324s (process:2636): libfprint-device-DEBUG: 05:02:23.910: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 324s (process:2636): libfprint-device-DEBUG: 05:02:23.910: Updated temperature model after 0.99 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 324s (process:2636): libfprint-device-DEBUG: 05:02:23.911: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.911: Activating image device 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.911: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.911: Image device activation completed 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.911: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.911: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 324s (process:2636): libfprint-device-DEBUG: 05:02:23.911: Device reported finger status change: FP_FINGER_STATUS_NEEDED 324s (process:2636): libfprint-virtual_image-DEBUG: 05:02:23.912: image data: 0x1da8a1b0 324s (process:2636): libfprint-device-DEBUG: 05:02:23.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.912: Image device reported finger status: on 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.912: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.912: Image device captured an image 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.912: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 324s (process:2636): libfprint-device-DEBUG: 05:02:23.912: Device reported finger status change: FP_FINGER_STATUS_PRESENT 324s (process:2636): libfprint-device-DEBUG: 05:02:23.912: Device reported finger status change: FP_FINGER_STATUS_NONE 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.912: Image device reported finger status: off 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.912: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.912: Deactivating image device 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.912: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.912: Image device deactivation completed 324s (process:2636): libfprint-image_device-DEBUG: 05:02:23.912: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 324s (process:2636): libfprint-image-DEBUG: 05:02:23.934: Minutiae scan completed in 0.021955 secs 324s (process:2636): libfprint-print-DEBUG: 05:02:23.941: score 10/40 325s (process:2636): libfprint-print-DEBUG: 05:02:23.946: score 10/40 325s (process:2636): libfprint-print-DEBUG: 05:02:23.952: score 10/40 325s (process:2636): libfprint-print-DEBUG: 05:02:23.958: score 10/40 325s (process:2636): libfprint-print-DEBUG: 05:02:23.963: score 10/40 325s Executing: libfprint-2/virtual-image.test 325s (process:2636): libfprint-print-DEBUG: 05:02:24.160: score 855/40 325s (process:2636): libfprint-device-DEBUG: 05:02:24.160: Device reported verify result 325s (process:2636): libfprint-device-DEBUG: 05:02:24.160: Device reported verify completion 325s (process:2636): libfprint-device-DEBUG: 05:02:24.160: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 325s (process:2636): libfprint-device-DEBUG: 05:02:24.160: Updated temperature model after 0.25 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 325s (process:2636): libfprint-device-DEBUG: 05:02:24.161: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.161: Activating image device 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.161: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.161: Image device activation completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.161: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.161: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 325s (process:2636): libfprint-device-DEBUG: 05:02:24.161: Device reported finger status change: FP_FINGER_STATUS_NEEDED 325s (process:2636): libfprint-device-DEBUG: 05:02:24.162: Device reported verify result 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.162: Deactivating image device 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.162: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.162: Image device deactivation completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.162: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 325s (process:2636): libfprint-device-DEBUG: 05:02:24.162: Device reported verify completion 325s (process:2636): libfprint-device-DEBUG: 05:02:24.162: Device reported finger status change: FP_FINGER_STATUS_NONE 325s (process:2636): libfprint-device-DEBUG: 05:02:24.162: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 325s (process:2636): libfprint-device-DEBUG: 05:02:24.162: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 325s (process:2636): libfprint-device-DEBUG: 05:02:24.162: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.163: Activating image device 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.163: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.163: Image device activation completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.163: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.163: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 325s (process:2636): libfprint-device-DEBUG: 05:02:24.163: Device reported finger status change: FP_FINGER_STATUS_NEEDED 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.163: Deactivating image device 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.163: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.163: Image device deactivation completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.163: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 325s (process:2636): libfprint-device-DEBUG: 05:02:24.163: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_VERIFY 325s (process:2636): libfprint-device-DEBUG: 05:02:24.163: Device reported verify completion 325s (process:2636): libfprint-device-DEBUG: 05:02:24.163: Device reported finger status change: FP_FINGER_STATUS_NONE 325s (process:2636): libfprint-device-DEBUG: 05:02:24.163: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 325s (process:2636): libfprint-device-DEBUG: 05:02:24.163: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 325s (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.164: 102082173: ../libfprint/drivers/virtual-image.c:244 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.264: Image device close completed 325s (process:2636): libfprint-device-DEBUG: 05:02:24.264: Device reported close completion 325s (process:2636): libfprint-device-DEBUG: 05:02:24.264: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 325s (process:2636): libfprint-device-DEBUG: 05:02:24.264: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 325s Print was processed, continuing 325s Print was processed, continuing 325s Print was processed, continuing 325s Print was processed, continuing 325s Print was processed, continuing 325s Enroll done 325s Print was processed, continuing 325s Print was processed, continuing 325s Print was processed, continuing 325s Print was processed, continuing 325s Print was processed, continuing 325s Enroll done 325s fp - device - error - quark: An unspecified error occurred! (0) 325s ok 325s test_features (__main__.VirtualImage.test_features) ... (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.264: 102183145: ../libfprint/drivers/virtual-image.c:216 325s (process:2636): libfprint-virtual_device_connection-DEBUG: 05:02:24.265: 102183203: ../libfprint/drivers/virtual-device-listener.c:153 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.364: Image device open completed 325s (process:2636): libfprint-device-DEBUG: 05:02:24.364: Device reported open completion 325s (process:2636): libfprint-device-DEBUG: 05:02:24.364: Completing action FPI_DEVICE_ACTION_OPEN in idle! 325s (process:2636): libfprint-device-DEBUG: 05:02:24.364: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 325s (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.365: 102283721: ../libfprint/drivers/virtual-image.c:244 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.465: Image device close completed 325s (process:2636): libfprint-device-DEBUG: 05:02:24.465: Device reported close completion 325s (process:2636): libfprint-device-DEBUG: 05:02:24.465: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 325s (process:2636): libfprint-device-DEBUG: 05:02:24.465: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 325s ok 325s test_identify (__main__.VirtualImage.test_identify) ... (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.465: 102384108: ../libfprint/drivers/virtual-image.c:216 325s (process:2636): libfprint-virtual_device_connection-DEBUG: 05:02:24.465: 102384165: ../libfprint/drivers/virtual-device-listener.c:153 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.565: Image device open completed 325s (process:2636): libfprint-device-DEBUG: 05:02:24.565: Device reported open completion 325s (process:2636): libfprint-device-DEBUG: 05:02:24.565: Completing action FPI_DEVICE_ACTION_OPEN in idle! 325s (process:2636): libfprint-device-DEBUG: 05:02:24.565: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 325s (process:2636): libfprint-device-DEBUG: 05:02:24.566: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.566: Activating image device 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.566: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.566: Image device activation completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.567: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.567: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 325s (process:2636): libfprint-device-DEBUG: 05:02:24.567: Device reported finger status change: FP_FINGER_STATUS_NEEDED 325s (process:2636): libfprint-virtual_device_connection-DEBUG: 05:02:24.567: Got a new connection! 325s (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.567: image data: 0x1da8a1b0 325s (process:2636): libfprint-device-DEBUG: 05:02:24.568: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.568: Image device reported finger status: on 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.568: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.568: Image device captured an image 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.568: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 325s (process:2636): libfprint-device-DEBUG: 05:02:24.568: Device reported finger status change: FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-device-DEBUG: 05:02:24.568: Device reported finger status change: FP_FINGER_STATUS_NONE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.568: Image device reported finger status: off 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.568: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image-DEBUG: 05:02:24.593: Minutiae scan completed in 0.025044 secs 325s (process:2636): libfprint-device-DEBUG: 05:02:24.594: Device reported enroll progress, reported 1 of 5 have been completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.594: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 325s (process:2636): libfprint-device-DEBUG: 05:02:24.594: Device reported finger status change: FP_FINGER_STATUS_NEEDED 325s (process:2636): libfprint-device-DEBUG: 05:02:24.594: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.594: Image device reported finger status: on 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.594: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 325s (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.595: image data: 0x1da8a1b0 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.595: Image device captured an image 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.595: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 325s (process:2636): libfprint-device-DEBUG: 05:02:24.595: Device reported finger status change: FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-image-DEBUG: 05:02:24.620: Minutiae scan completed in 0.024975 secs 325s (process:2636): libfprint-device-DEBUG: 05:02:24.620: Device reported enroll progress, reported 2 of 5 have been completed 325s (process:2636): libfprint-device-DEBUG: 05:02:24.621: Device reported finger status change: FP_FINGER_STATUS_NONE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.621: Image device reported finger status: off 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.621: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.621: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 325s (process:2636): libfprint-device-DEBUG: 05:02:24.621: Device reported finger status change: FP_FINGER_STATUS_NEEDED 325s (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.622: image data: 0x1da8a1b0 325s (process:2636): libfprint-device-DEBUG: 05:02:24.622: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.622: Image device reported finger status: on 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.622: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.622: Image device captured an image 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.622: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 325s (process:2636): libfprint-device-DEBUG: 05:02:24.622: Device reported finger status change: FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-device-DEBUG: 05:02:24.622: Device reported finger status change: FP_FINGER_STATUS_NONE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.622: Image device reported finger status: off 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.622: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image-DEBUG: 05:02:24.647: Minutiae scan completed in 0.024628 secs 325s (process:2636): libfprint-device-DEBUG: 05:02:24.647: Device reported enroll progress, reported 3 of 5 have been completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.647: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 325s (process:2636): libfprint-device-DEBUG: 05:02:24.647: Device reported finger status change: FP_FINGER_STATUS_NEEDED 325s (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.648: image data: 0x1da8a1b0 325s (process:2636): libfprint-device-DEBUG: 05:02:24.648: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.648: Image device reported finger status: on 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.648: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.648: Image device captured an image 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.648: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 325s (process:2636): libfprint-device-DEBUG: 05:02:24.648: Device reported finger status change: FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-device-DEBUG: 05:02:24.649: Device reported finger status change: FP_FINGER_STATUS_NONE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.649: Image device reported finger status: off 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.649: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image-DEBUG: 05:02:24.673: Minutiae scan completed in 0.024812 secs 325s (process:2636): libfprint-device-DEBUG: 05:02:24.674: Device reported enroll progress, reported 4 of 5 have been completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.674: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 325s (process:2636): libfprint-device-DEBUG: 05:02:24.674: Device reported finger status change: FP_FINGER_STATUS_NEEDED 325s (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.675: image data: 0x1da8a1b0 325s (process:2636): libfprint-device-DEBUG: 05:02:24.675: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.675: Image device reported finger status: on 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.675: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.675: Image device captured an image 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.675: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 325s (process:2636): libfprint-device-DEBUG: 05:02:24.675: Device reported finger status change: FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-device-DEBUG: 05:02:24.675: Device reported finger status change: FP_FINGER_STATUS_NONE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.675: Image device reported finger status: off 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.675: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image-DEBUG: 05:02:24.700: Minutiae scan completed in 0.024744 secs 325s (process:2636): libfprint-device-DEBUG: 05:02:24.701: Device reported enroll progress, reported 5 of 5 have been completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.701: Deactivating image device 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.701: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.701: Image device deactivation completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.701: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 325s (process:2636): libfprint-device-DEBUG: 05:02:24.701: Device reported enroll completion 325s (process:2636): libfprint-device-DEBUG: 05:02:24.701: Print for finger FP_FINGER_LEFT_THUMB enrolled 325s (process:2636): libfprint-device-DEBUG: 05:02:24.701: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 325s (process:2636): libfprint-device-DEBUG: 05:02:24.701: Updated temperature model after 0.13 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 325s (process:2636): libfprint-device-DEBUG: 05:02:24.702: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.702: Activating image device 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.702: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.702: Image device activation completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.702: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.702: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 325s (process:2636): libfprint-device-DEBUG: 05:02:24.702: Device reported finger status change: FP_FINGER_STATUS_NEEDED 325s (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.703: image data: 0x1da8a1b0 325s (process:2636): libfprint-device-DEBUG: 05:02:24.703: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.703: Image device reported finger status: on 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.703: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.703: Image device captured an image 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.703: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 325s (process:2636): libfprint-device-DEBUG: 05:02:24.703: Device reported finger status change: FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-device-DEBUG: 05:02:24.703: Device reported finger status change: FP_FINGER_STATUS_NONE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.703: Image device reported finger status: off 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.703: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image-DEBUG: 05:02:24.726: Minutiae scan completed in 0.022656 secs 325s (process:2636): libfprint-device-DEBUG: 05:02:24.727: Device reported enroll progress, reported 1 of 5 have been completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.727: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 325s (process:2636): libfprint-device-DEBUG: 05:02:24.727: Device reported finger status change: FP_FINGER_STATUS_NEEDED 325s (process:2636): libfprint-device-DEBUG: 05:02:24.728: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.728: Image device reported finger status: on 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.728: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 325s (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.729: image data: 0x1da8a1b0 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.729: Image device captured an image 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.729: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 325s (process:2636): libfprint-device-DEBUG: 05:02:24.730: Device reported finger status change: FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-image-DEBUG: 05:02:24.753: Minutiae scan completed in 0.022552 secs 325s (process:2636): libfprint-device-DEBUG: 05:02:24.753: Device reported enroll progress, reported 2 of 5 have been completed 325s (process:2636): libfprint-device-DEBUG: 05:02:24.754: Device reported finger status change: FP_FINGER_STATUS_NONE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.754: Image device reported finger status: off 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.754: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.754: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 325s (process:2636): libfprint-device-DEBUG: 05:02:24.754: Device reported finger status change: FP_FINGER_STATUS_NEEDED 325s (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.755: image data: 0x1da8a1b0 325s (process:2636): libfprint-device-DEBUG: 05:02:24.756: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.756: Image device reported finger status: on 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.756: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.756: Image device captured an image 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.756: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 325s (process:2636): libfprint-device-DEBUG: 05:02:24.757: Device reported finger status change: FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-device-DEBUG: 05:02:24.757: Device reported finger status change: FP_FINGER_STATUS_NONE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.757: Image device reported finger status: off 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.757: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image-DEBUG: 05:02:24.779: Minutiae scan completed in 0.022871 secs 325s (process:2636): libfprint-device-DEBUG: 05:02:24.780: Device reported enroll progress, reported 3 of 5 have been completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.780: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 325s (process:2636): libfprint-device-DEBUG: 05:02:24.780: Device reported finger status change: FP_FINGER_STATUS_NEEDED 325s (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.781: image data: 0x1da8a1b0 325s (process:2636): libfprint-device-DEBUG: 05:02:24.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.781: Image device reported finger status: on 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.781: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.781: Image device captured an image 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.781: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 325s (process:2636): libfprint-device-DEBUG: 05:02:24.781: Device reported finger status change: FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-device-DEBUG: 05:02:24.781: Device reported finger status change: FP_FINGER_STATUS_NONE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.781: Image device reported finger status: off 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.781: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image-DEBUG: 05:02:24.804: Minutiae scan completed in 0.022317 secs 325s (process:2636): libfprint-device-DEBUG: 05:02:24.804: Device reported enroll progress, reported 4 of 5 have been completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.804: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 325s (process:2636): libfprint-device-DEBUG: 05:02:24.805: Device reported finger status change: FP_FINGER_STATUS_NEEDED 325s (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.805: image data: 0x1da8a1b0 325s (process:2636): libfprint-device-DEBUG: 05:02:24.806: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.806: Image device reported finger status: on 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.806: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.806: Image device captured an image 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.806: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 325s (process:2636): libfprint-device-DEBUG: 05:02:24.806: Device reported finger status change: FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-device-DEBUG: 05:02:24.806: Device reported finger status change: FP_FINGER_STATUS_NONE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.806: Image device reported finger status: off 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.806: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image-DEBUG: 05:02:24.829: Minutiae scan completed in 0.022863 secs 325s (process:2636): libfprint-device-DEBUG: 05:02:24.829: Device reported enroll progress, reported 5 of 5 have been completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.830: Deactivating image device 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.830: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.830: Image device deactivation completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.830: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 325s (process:2636): libfprint-device-DEBUG: 05:02:24.830: Device reported enroll completion 325s (process:2636): libfprint-device-DEBUG: 05:02:24.830: Print for finger FP_FINGER_LEFT_THUMB enrolled 325s (process:2636): libfprint-device-DEBUG: 05:02:24.830: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 325s (process:2636): libfprint-device-DEBUG: 05:02:24.830: Updated temperature model after 0.13 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 325s (process:2636): libfprint-device-DEBUG: 05:02:24.831: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.831: Activating image device 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.831: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.831: Image device activation completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.831: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.831: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 325s (process:2636): libfprint-device-DEBUG: 05:02:24.831: Device reported finger status change: FP_FINGER_STATUS_NEEDED 325s (process:2636): libfprint-virtual_image-DEBUG: 05:02:24.832: image data: 0x1da8a310 325s (process:2636): libfprint-device-DEBUG: 05:02:24.832: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.832: Image device reported finger status: on 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.832: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.832: Image device captured an image 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.832: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 325s (process:2636): libfprint-device-DEBUG: 05:02:24.832: Device reported finger status change: FP_FINGER_STATUS_PRESENT 325s (process:2636): libfprint-device-DEBUG: 05:02:24.832: Device reported finger status change: FP_FINGER_STATUS_NONE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.832: Image device reported finger status: off 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.832: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.832: Deactivating image device 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.832: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.832: Image device deactivation completed 325s (process:2636): libfprint-image_device-DEBUG: 05:02:24.832: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 325s (process:2636): libfprint-image-DEBUG: 05:02:24.855: Minutiae scan completed in 0.022475 secs 325s (process:2636): libfprint-print-DEBUG: 05:02:24.862: score 10/40 325s (process:2636): libfprint-print-DEBUG: 05:02:24.868: score 10/40 325s (process:2636): libfprint-print-DEBUG: 05:02:24.874: score 10/40 325s (process:2636): libfprint-print-DEBUG: 05:02:24.879: score 10/40 325s (process:2636): libfprint-print-DEBUG: 05:02:24.885: score 10/40 326s (process:2636): libfprint-print-DEBUG: 05:02:25.082: score 855/40 326s (process:2636): libfprint-device-DEBUG: 05:02:25.082: Device reported identify result 326s (process:2636): libfprint-device-DEBUG: 05:02:25.082: Device reported identify completion 326s (process:2636): libfprint-device-DEBUG: 05:02:25.082: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 326s (process:2636): libfprint-device-DEBUG: 05:02:25.082: Updated temperature model after 0.25 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 326s (process:2636): libfprint-device-DEBUG: 05:02:25.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.083: Activating image device 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.083: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.083: Image device activation completed 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.083: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.083: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 326s (process:2636): libfprint-device-DEBUG: 05:02:25.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED 326s (process:2636): libfprint-virtual_image-DEBUG: 05:02:25.084: image data: 0x1da99750 326s (process:2636): libfprint-device-DEBUG: 05:02:25.084: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.085: Image device reported finger status: on 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.085: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.085: Image device captured an image 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.085: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 326s (process:2636): libfprint-device-DEBUG: 05:02:25.085: Device reported finger status change: FP_FINGER_STATUS_PRESENT 326s (process:2636): libfprint-device-DEBUG: 05:02:25.085: Device reported finger status change: FP_FINGER_STATUS_NONE 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.085: Image device reported finger status: off 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.085: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.085: Deactivating image device 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.085: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.085: Image device deactivation completed 326s (process:2636): libfprint-image_device-DEBUG: 05:02:25.085: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 326s (process:2636): libfprint-image-DEBUG: 05:02:25.110: Minutiae scan completed in 0.024839 secs 327s (process:2636): libfprint-print-DEBUG: 05:02:26.077: score 1093/40 327s (process:2636): libfprint-device-DEBUG: 05:02:26.078: Device reported identify result 327s (process:2636): libfprint-device-DEBUG: 05:02:26.078: Device reported identify completion 327s (process:2636): libfprint-device-DEBUG: 05:02:26.078: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 327s (process:2636): libfprint-device-DEBUG: 05:02:26.078: Updated temperature model after 0.99 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 327s (process:2636): libfprint-device-DEBUG: 05:02:26.078: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.078: Activating image device 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.078: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.078: Image device activation completed 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.078: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.078: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 327s (process:2636): libfprint-device-DEBUG: 05:02:26.078: Device reported finger status change: FP_FINGER_STATUS_NEEDED 327s (process:2636): libfprint-device-DEBUG: 05:02:26.079: Device reported identify result 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.079: Deactivating image device 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.079: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.079: Image device deactivation completed 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.079: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 327s (process:2636): libfprint-device-DEBUG: 05:02:26.079: Device reported identify completion 327s (process:2636): libfprint-device-DEBUG: 05:02:26.079: Device reported finger status change: FP_FINGER_STATUS_NONE 327s (process:2636): libfprint-device-DEBUG: 05:02:26.079: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 327s (process:2636): libfprint-device-DEBUG: 05:02:26.079: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 327s (process:2636): libfprint-device-DEBUG: 05:02:26.080: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.080: Activating image device 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.080: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.080: Image device activation completed 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.080: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.080: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 327s (process:2636): libfprint-device-DEBUG: 05:02:26.080: Device reported finger status change: FP_FINGER_STATUS_NEEDED 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.080: Deactivating image device 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.080: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.080: Image device deactivation completed 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.080: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 327s (process:2636): libfprint-device-DEBUG: 05:02:26.080: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_IDENTIFY 327s (process:2636): libfprint-device-DEBUG: 05:02:26.080: Device reported identify completion 327s (process:2636): libfprint-device-DEBUG: 05:02:26.080: Device reported finger status change: FP_FINGER_STATUS_NONE 327s (process:2636): libfprint-device-DEBUG: 05:02:26.080: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 327s (process:2636): libfprint-device-DEBUG: 05:02:26.080: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 327s (process:2636): libfprint-virtual_image-DEBUG: 05:02:26.080: 103999150: ../libfprint/drivers/virtual-image.c:244 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.181: Image device close completed 327s (process:2636): libfprint-device-DEBUG: 05:02:26.181: Device reported close completion 327s (process:2636): libfprint-device-DEBUG: 05:02:26.181: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 327s (process:2636): libfprint-device-DEBUG: 05:02:26.181: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 327s Print was processed, continuing 327s Print was processed, continuing 327s Print was processed, continuing 327s Print was processed, continuing 327s Print was processed, continuing 327s Enroll done 327s Print was processed, continuing 327s Print was processed, continuing 327s Print was processed, continuing 327s Print was processed, continuing 327s Print was processed, continuing 327s Enroll done 327s Identify finished 327s Identify finished 327s Identify finished 327s fp - device - retry - quark: The swipe was too short, please try again. (1) 327s Identify finished 327s fp - device - error - quark: An unspecified error occurred! (0) 327s ok 327s test_verify_serialized (__main__.VirtualImage.test_verify_serialized) ... (process:2636): libfprint-virtual_image-DEBUG: 05:02:26.182: 104100189: ../libfprint/drivers/virtual-image.c:216 327s (process:2636): libfprint-virtual_device_connection-DEBUG: 05:02:26.182: 104100257: ../libfprint/drivers/virtual-device-listener.c:153 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.281: Image device open completed 327s (process:2636): libfprint-device-DEBUG: 05:02:26.281: Device reported open completion 327s (process:2636): libfprint-device-DEBUG: 05:02:26.281: Completing action FPI_DEVICE_ACTION_OPEN in idle! 327s (process:2636): libfprint-device-DEBUG: 05:02:26.281: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 327s (process:2636): libfprint-device-DEBUG: 05:02:26.283: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.283: Activating image device 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.283: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.283: Image device activation completed 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.283: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.283: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 327s (process:2636): libfprint-device-DEBUG: 05:02:26.283: Device reported finger status change: FP_FINGER_STATUS_NEEDED 327s (process:2636): libfprint-virtual_device_connection-DEBUG: 05:02:26.284: Got a new connection! 327s (process:2636): libfprint-virtual_image-DEBUG: 05:02:26.284: image data: 0x1da99750 327s (process:2636): libfprint-device-DEBUG: 05:02:26.284: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.285: Image device reported finger status: on 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.285: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.285: Image device captured an image 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.285: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 327s (process:2636): libfprint-device-DEBUG: 05:02:26.285: Device reported finger status change: FP_FINGER_STATUS_PRESENT 327s (process:2636): libfprint-device-DEBUG: 05:02:26.285: Device reported finger status change: FP_FINGER_STATUS_NONE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.285: Image device reported finger status: off 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.285: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 327s (process:2636): libfprint-image-DEBUG: 05:02:26.310: Minutiae scan completed in 0.025026 secs 327s (process:2636): libfprint-device-DEBUG: 05:02:26.311: Device reported enroll progress, reported 1 of 5 have been completed 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.311: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 327s (process:2636): libfprint-device-DEBUG: 05:02:26.311: Device reported finger status change: FP_FINGER_STATUS_NEEDED 327s (process:2636): libfprint-device-DEBUG: 05:02:26.312: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.312: Image device reported finger status: on 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.312: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 327s (process:2636): libfprint-virtual_image-DEBUG: 05:02:26.312: image data: 0x1daa7fe0 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.313: Image device captured an image 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.313: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 327s (process:2636): libfprint-device-DEBUG: 05:02:26.313: Device reported finger status change: FP_FINGER_STATUS_PRESENT 327s (process:2636): libfprint-image-DEBUG: 05:02:26.338: Minutiae scan completed in 0.025227 secs 327s (process:2636): libfprint-device-DEBUG: 05:02:26.339: Device reported enroll progress, reported 2 of 5 have been completed 327s (process:2636): libfprint-device-DEBUG: 05:02:26.340: Device reported finger status change: FP_FINGER_STATUS_NONE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.340: Image device reported finger status: off 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.340: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.340: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 327s (process:2636): libfprint-device-DEBUG: 05:02:26.340: Device reported finger status change: FP_FINGER_STATUS_NEEDED 327s (process:2636): libfprint-virtual_image-DEBUG: 05:02:26.341: image data: 0x1daa7fe0 327s (process:2636): libfprint-device-DEBUG: 05:02:26.341: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.341: Image device reported finger status: on 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.341: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.341: Image device captured an image 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.341: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 327s (process:2636): libfprint-device-DEBUG: 05:02:26.341: Device reported finger status change: FP_FINGER_STATUS_PRESENT 327s (process:2636): libfprint-device-DEBUG: 05:02:26.341: Device reported finger status change: FP_FINGER_STATUS_NONE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.341: Image device reported finger status: off 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.341: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 327s (process:2636): libfprint-image-DEBUG: 05:02:26.366: Minutiae scan completed in 0.025044 secs 327s (process:2636): libfprint-device-DEBUG: 05:02:26.367: Device reported enroll progress, reported 3 of 5 have been completed 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.368: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 327s (process:2636): libfprint-device-DEBUG: 05:02:26.368: Device reported finger status change: FP_FINGER_STATUS_NEEDED 327s (process:2636): libfprint-virtual_image-DEBUG: 05:02:26.368: image data: 0x1daa7fe0 327s (process:2636): libfprint-device-DEBUG: 05:02:26.369: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.369: Image device reported finger status: on 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.369: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.369: Image device captured an image 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.369: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 327s (process:2636): libfprint-device-DEBUG: 05:02:26.369: Device reported finger status change: FP_FINGER_STATUS_PRESENT 327s (process:2636): libfprint-device-DEBUG: 05:02:26.369: Device reported finger status change: FP_FINGER_STATUS_NONE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.369: Image device reported finger status: off 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.369: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 327s (process:2636): libfprint-image-DEBUG: 05:02:26.395: Minutiae scan completed in 0.025830 secs 327s (process:2636): libfprint-device-DEBUG: 05:02:26.395: Device reported enroll progress, reported 4 of 5 have been completed 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.396: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 327s (process:2636): libfprint-device-DEBUG: 05:02:26.396: Device reported finger status change: FP_FINGER_STATUS_NEEDED 327s (process:2636): libfprint-virtual_image-DEBUG: 05:02:26.396: image data: 0x1daa7fe0 327s (process:2636): libfprint-device-DEBUG: 05:02:26.397: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.397: Image device reported finger status: on 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.397: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.397: Image device captured an image 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.397: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 327s (process:2636): libfprint-device-DEBUG: 05:02:26.397: Device reported finger status change: FP_FINGER_STATUS_PRESENT 327s (process:2636): libfprint-device-DEBUG: 05:02:26.397: Device reported finger status change: FP_FINGER_STATUS_NONE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.398: Image device reported finger status: off 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.398: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 327s (process:2636): libfprint-image-DEBUG: 05:02:26.422: Minutiae scan completed in 0.024848 secs 327s (process:2636): libfprint-device-DEBUG: 05:02:26.423: Device reported enroll progress, reported 5 of 5 have been completed 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.423: Deactivating image device 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.423: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.423: Image device deactivation completed 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.423: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 327s (process:2636): libfprint-device-DEBUG: 05:02:26.423: Device reported enroll completion 327s (process:2636): libfprint-device-DEBUG: 05:02:26.423: Print for finger FP_FINGER_LEFT_THUMB enrolled 327s (process:2636): libfprint-device-DEBUG: 05:02:26.424: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 327s (process:2636): libfprint-device-DEBUG: 05:02:26.424: Updated temperature model after 0.14 seconds, ratio 0.28 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 327s (process:2636): libfprint-device-DEBUG: 05:02:26.425: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.425: Activating image device 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.425: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.425: Image device activation completed 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.425: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.425: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 327s (process:2636): libfprint-device-DEBUG: 05:02:26.425: Device reported finger status change: FP_FINGER_STATUS_NEEDED 327s (process:2636): libfprint-virtual_image-DEBUG: 05:02:26.426: image data: 0x1daa7fe0 327s (process:2636): libfprint-device-DEBUG: 05:02:26.426: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.426: Image device reported finger status: on 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.426: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.426: Image device captured an image 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.428: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 327s (process:2636): libfprint-device-DEBUG: 05:02:26.428: Device reported finger status change: FP_FINGER_STATUS_PRESENT 327s (process:2636): libfprint-device-DEBUG: 05:02:26.428: Device reported finger status change: FP_FINGER_STATUS_NONE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.428: Image device reported finger status: off 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.428: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.428: Deactivating image device 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.428: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.428: Image device deactivation completed 327s (process:2636): libfprint-image_device-DEBUG: 05:02:26.428: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 327s (process:2636): libfprint-image-DEBUG: 05:02:26.452: Minutiae scan completed in 0.025165 secs 328s (process:2636): libfprint-print-DEBUG: 05:02:27.438: score 1093/40 328s (process:2636): libfprint-device-DEBUG: 05:02:27.438: Device reported verify result 328s (process:2636): libfprint-device-DEBUG: 05:02:27.438: Device reported verify completion 328s (process:2636): libfprint-device-DEBUG: 05:02:27.438: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 328s (process:2636): libfprint-device-DEBUG: 05:02:27.438: Updated temperature model after 1.01 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 328s (process:2636): libfprint-device-DEBUG: 05:02:27.438: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.438: Activating image device 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.438: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.438: Image device activation completed 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.438: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.438: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 328s (process:2636): libfprint-device-DEBUG: 05:02:27.438: Device reported finger status change: FP_FINGER_STATUS_NEEDED 328s (process:2636): libfprint-virtual_image-DEBUG: 05:02:27.439: image data: 0x1daa8790 328s (process:2636): libfprint-device-DEBUG: 05:02:27.439: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.439: Image device reported finger status: on 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.439: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.439: Image device captured an image 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.441: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 328s (process:2636): libfprint-device-DEBUG: 05:02:27.441: Device reported finger status change: FP_FINGER_STATUS_PRESENT 328s (process:2636): libfprint-device-DEBUG: 05:02:27.441: Device reported finger status change: FP_FINGER_STATUS_NONE 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.441: Image device reported finger status: off 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.441: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.441: Deactivating image device 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.441: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.441: Image device deactivation completed 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.441: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 328s (process:2636): libfprint-image-DEBUG: 05:02:27.460: Minutiae scan completed in 0.021288 secs 328s (process:2636): libfprint-print-DEBUG: 05:02:27.466: score 10/40 328s (process:2636): libfprint-print-DEBUG: 05:02:27.472: score 10/40 328s (process:2636): libfprint-print-DEBUG: 05:02:27.477: score 10/40 328s (process:2636): libfprint-print-DEBUG: 05:02:27.483: score 10/40 328s (process:2636): libfprint-print-DEBUG: 05:02:27.488: score 10/40 328s (process:2636): libfprint-device-DEBUG: 05:02:27.488: Device reported verify result 328s (process:2636): libfprint-device-DEBUG: 05:02:27.488: Device reported verify completion 328s (process:2636): libfprint-device-DEBUG: 05:02:27.488: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 328s (process:2636): libfprint-device-DEBUG: 05:02:27.488: Updated temperature model after 0.05 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 328s (process:2636): libfprint-virtual_image-DEBUG: 05:02:27.489: 105407288: ../libfprint/drivers/virtual-image.c:244 328s (process:2636): libfprint-image_device-DEBUG: 05:02:27.589: Image device close completed 328s (process:2636): libfprint-device-DEBUG: 05:02:27.589: Device reported close completion 328s (process:2636): libfprint-device-DEBUG: 05:02:27.589: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 328s (process:2636): libfprint-device-DEBUG: 05:02:27.589: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 328s Print was processed, continuing 328s Print was processed, continuing 328s Print was processed, continuing 328s Print was processed, continuing 328s Print was processed, continuing 328s Enroll done 328s ok 328s 328s ---------------------------------------------------------------------- 328s Ran 5 tests in 6.281s 328s 328s OK 328s PASS: libfprint-2/virtual-image.test 328s Running test: libfprint-2/fpi-ssm.test 328s TAP version 14 328s # random seed: R02S3abba5d14a3827d193f05053e505d867 328s 1..42 328s # Start of ssm tests 328s ok 1 /ssm/new 328s ok 2 /ssm/set_data 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 328s ok 3 /ssm/start 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 328s ok 4 /ssm/next 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 328s ok 5 /ssm/jump_to_state 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 328s ok 6 /ssm/mark_completed 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 328s # 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. 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 328s ok 7 /ssm/mark_failed 328s # Start of new tests 328s ok 8 /ssm/new/full 328s ok 9 /ssm/new/no_handler 328s ok 10 /ssm/new/wrong_states 328s # End of new tests 328s # Start of set_data tests 328s ok 11 /ssm/set_data/cleanup 328s # End of set_data tests 328s # Start of start tests 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE entering state 0 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE completed successfully 328s ok 12 /ssm/start/single 328s # End of start tests 328s # Start of next tests 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 328s ok 13 /ssm/next/complete 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 328s ok 14 /ssm/next/not_started 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 328s ok 15 /ssm/next/with_delayed 328s # End of next tests 328s # Start of jump_to_state tests 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 328s ok 16 /ssm/jump_to_state/not_started 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 328s ok 17 /ssm/jump_to_state/with_delayed 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 328s ok 18 /ssm/jump_to_state/last 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 328s ok 19 /ssm/jump_to_state/wrong 328s # End of jump_to_state tests 328s # Start of mark_completed tests 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 328s ok 20 /ssm/mark_completed/not_started 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 328s ok 21 /ssm/mark_completed/with_delayed 328s # End of mark_completed tests 328s # Start of mark_failed tests 328s # 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. 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 328s ok 22 /ssm/mark_failed/not_started 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 328s # 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. 328s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device. 329s ok 23 /ssm/mark_failed/with_delayed 329s # End of mark_failed tests 329s # Start of delayed tests 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 329s ok 24 /ssm/delayed/next 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 329s ok 25 /ssm/delayed/jump_to_state 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 329s ok 26 /ssm/delayed/mark_completed 329s # Start of next tests 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 329s ok 27 /ssm/delayed/next/cancel 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 329s ok 28 /ssm/delayed/next/not_started 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 329s ok 29 /ssm/delayed/next/complete 329s # End of next tests 329s # Start of jump_to_state tests 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 329s ok 30 /ssm/delayed/jump_to_state/cancel 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 329s ok 31 /ssm/delayed/jump_to_state/not_started 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 329s ok 32 /ssm/delayed/jump_to_state/last 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10 329s ok 33 /ssm/delayed/jump_to_state/wrong 329s # End of jump_to_state tests 329s # Start of mark_completed tests 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 329s ok 34 /ssm/delayed/mark_completed/cancel 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 329s ok 35 /ssm/delayed/mark_completed/not_started 329s # End of mark_completed tests 329s # Start of cancel tests 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change 329s ok 36 /ssm/delayed/cancel/error 329s # End of cancel tests 329s # End of delayed tests 329s # Start of subssm tests 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 1 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 329s ok 37 /ssm/subssm/start 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 329s # 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. 329s # 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. 329s # 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. 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later. 329s ok 38 /ssm/subssm/mark_failed 329s # Start of start tests 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 329s ok 39 /ssm/subssm/start/with_started 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1 329s ok 40 /ssm/subssm/start/with_delayed 329s # End of start tests 329s # End of subssm tests 329s # Start of cleanup tests 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully 329s ok 41 /ssm/cleanup/complete 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0 329s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2 329s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3 329s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2 329s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: non-cleanup 329s ok 42 /ssm/cleanup/fail 329s # End of cleanup tests 329s # End of ssm tests 329s PASS: libfprint-2/fpi-ssm.test 329s Running test: libfprint-2/driver-vfs301.test 329s ** (umockdev-run:2647): DEBUG: 05:02:28.727: umockdev.vala:127: Created udev test bed /tmp/umockdev.32W212 329s ** (umockdev-run:2647): DEBUG: 05:02:28.727: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 329s ** (umockdev-run:2647): DEBUG: 05:02:28.729: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3 (subsystem usb) 329s ** (umockdev-run:2647): DEBUG: 05:02:28.731: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.32W212/dev/bus/usb/002/005 329s ** (umockdev-run:2647): DEBUG: 05:02:28.731: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2/2-1 329s ** (umockdev-run:2647): DEBUG: 05:02:28.732: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2/2-1 (subsystem usb) 329s ** (umockdev-run:2647): DEBUG: 05:02:28.734: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.32W212/dev/bus/usb/002/002 329s ** (umockdev-run:2647): DEBUG: 05:02:28.734: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0/usb2 329s ** (umockdev-run:2647): DEBUG: 05:02:28.735: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0/usb2 (subsystem usb) 329s ** (umockdev-run:2647): DEBUG: 05:02:28.737: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.32W212/dev/bus/usb/002/001 329s ** (umockdev-run:2647): DEBUG: 05:02:28.737: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1d.0 329s ** (umockdev-run:2647): DEBUG: 05:02:28.738: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1d.0 (subsystem pci) 329s (umockdev-run:2647): GLib-GIO-DEBUG: 05:02:28.739: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 329s (process:2651): libfprint-context-DEBUG: 05:02:28.866: Initializing FpContext (libfprint version 1.94.9+tod1) 329s (process:2651): libfprint-tod-DEBUG: 05:02:28.866: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 329s (process:2651): libfprint-context-DEBUG: 05:02:28.868: No driver found for USB device 8087:0020 329s (process:2651): libfprint-context-DEBUG: 05:02:28.868: No driver found for USB device 1D6B:0002 329s (process:2651): libfprint-device-DEBUG: 05:02:28.869: Device reported probe completion 329s (process:2651): libfprint-device-DEBUG: 05:02:28.869: Completing action FPI_DEVICE_ACTION_PROBE in idle! 329s (process:2651): libfprint-device-DEBUG: 05:02:28.869: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 329s (process:2651): libfprint-image_device-DEBUG: 05:02:28.870: Image device open completed 329s (process:2651): libfprint-device-DEBUG: 05:02:28.870: Device reported open completion 329s (process:2651): libfprint-device-DEBUG: 05:02:28.870: Completing action FPI_DEVICE_ACTION_OPEN in idle! 329s (process:2651): libfprint-device-DEBUG: 05:02:28.870: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 329s (process:2651): libfprint-device-DEBUG: 05:02:28.871: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 329s (process:2651): libfprint-image_device-DEBUG: 05:02:28.871: Activating image device 329s (process:2651): libfprint-image_device-DEBUG: 05:02:28.871: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 329s (process:2651): libfprint-SSM-DEBUG: 05:02:28.871: [vfs301] 1 entering state 0 329s (process:2651): libfprint-SSM-DEBUG: 05:02:28.907: [vfs301] 1 completed successfully 329s (process:2651): libfprint-image_device-DEBUG: 05:02:28.907: Image device activation completed 329s (process:2651): libfprint-image_device-DEBUG: 05:02:28.907: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 329s (process:2651): libfprint-image_device-DEBUG: 05:02:28.907: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 329s (process:2651): libfprint-SSM-DEBUG: 05:02:28.907: [vfs301] M_LOOP_NUM_STATES entering state 0 329s (process:2651): libfprint-SSM-DEBUG: 05:02:28.908: [vfs301] M_LOOP_NUM_STATES entering state 1 329s (process:2651): libfprint-device-DEBUG: 05:02:28.908: Device reported finger status change: FP_FINGER_STATUS_NEEDED 330s (process:2651): libfprint-device-DEBUG: 05:02:28.970: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 330s Executing: libfprint-2/driver-vfs301.test 330s (process:2651): libfprint-SSM-DEBUG: 05:02:29.108: [vfs301] M_LOOP_NUM_STATES entering state 2 330s (process:2651): libfprint-SSM-DEBUG: 05:02:29.109: [vfs301] M_LOOP_NUM_STATES entering state 1 330s (process:2651): libfprint-SSM-DEBUG: 05:02:29.309: [vfs301] M_LOOP_NUM_STATES entering state 2 330s (process:2651): libfprint-SSM-DEBUG: 05:02:29.310: [vfs301] M_LOOP_NUM_STATES entering state 3 330s (process:2651): libfprint-device-DEBUG: 05:02:29.310: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 330s (process:2651): libfprint-image_device-DEBUG: 05:02:29.310: Image device reported finger status: on 330s (process:2651): libfprint-image_device-DEBUG: 05:02:29.310: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 330s (process:2651): libfprint-SSM-DEBUG: 05:02:29.311: [vfs301] M_LOOP_NUM_STATES entering state 4 330s (process:2651): libfprint-SSM-DEBUG: 05:02:29.511: [vfs301] M_LOOP_NUM_STATES entering state 5 330s (process:2651): libfprint-SSM-DEBUG: 05:02:29.514: [vfs301] M_LOOP_NUM_STATES entering state 6 330s (process:2651): libfprint-image_device-DEBUG: 05:02:29.514: Image device captured an image 330s (process:2651): libfprint-image_device-DEBUG: 05:02:29.515: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 330s (process:2651): libfprint-device-DEBUG: 05:02:29.515: Device reported finger status change: FP_FINGER_STATUS_PRESENT 330s (process:2651): libfprint-SSM-DEBUG: 05:02:29.515: [vfs301] M_LOOP_NUM_STATES completed successfully 330s (process:2651): libfprint-device-DEBUG: 05:02:29.515: Device reported finger status change: FP_FINGER_STATUS_NONE 330s (process:2651): libfprint-image_device-DEBUG: 05:02:29.515: Image device reported finger status: off 330s (process:2651): libfprint-image_device-DEBUG: 05:02:29.515: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 330s (process:2651): libfprint-image_device-DEBUG: 05:02:29.515: Deactivating image device 330s (process:2651): libfprint-image_device-DEBUG: 05:02:29.515: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 330s (process:2651): libfprint-image_device-DEBUG: 05:02:29.515: Image device deactivation completed 330s (process:2651): libfprint-image_device-DEBUG: 05:02:29.515: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 330s (process:2651): libfprint-image-DEBUG: 05:02:29.537: Minutiae scan completed in 0.022500 secs 330s (process:2651): libfprint-device-DEBUG: 05:02:29.538: Device reported capture completion 330s (process:2651): libfprint-device-DEBUG: 05:02:29.538: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 330s (process:2651): libfprint-device-DEBUG: 05:02:29.538: Updated temperature model after 0.57 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 330s (process:2651): libfprint-image_device-DEBUG: 05:02:29.538: Image device close completed 330s (process:2651): libfprint-device-DEBUG: 05:02:29.538: Device reported close completion 330s (process:2651): libfprint-device-DEBUG: 05:02:29.539: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 330s (process:2651): libfprint-device-DEBUG: 05:02:29.539: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 330s ** (umockdev-run:2647): DEBUG: 05:02:29.629: umockdev.vala:154: Removing test bed /tmp/umockdev.32W212 330s (umockdev-run:2647): GLib-DEBUG: 05:02:29.635: unsetenv() is not thread-safe and should not be used after threads are created 330s Comparing PNGs /tmp/libfprint-umockdev-test-470zry4x/capture.png and /usr/share/installed-tests/libfprint-2/vfs301/capture.png 330s PASS: libfprint-2/driver-vfs301.test 330s Running test: libfprint-2/driver-nb1010.test 330s ** (umockdev-run:2660): DEBUG: 05:02:29.713: umockdev.vala:127: Created udev test bed /tmp/umockdev.9FX412 330s ** (umockdev-run:2660): DEBUG: 05:02:29.714: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 330s ** (umockdev-run:2660): DEBUG: 05:02:29.717: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 (subsystem usb) 330s ** (umockdev-run:2660): DEBUG: 05:02:29.720: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.9FX412/dev/bus/usb/001/003 330s ** (umockdev-run:2660): DEBUG: 05:02:29.720: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 330s ** (umockdev-run:2660): DEBUG: 05:02:29.723: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 (subsystem usb) 330s ** (umockdev-run:2660): DEBUG: 05:02:29.726: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.9FX412/dev/bus/usb/001/001 330s ** (umockdev-run:2660): DEBUG: 05:02:29.726: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0 330s ** (umockdev-run:2660): DEBUG: 05:02:29.728: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0 (subsystem pci) 330s ** (umockdev-run:2660): DEBUG: 05:02:29.730: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3 330s ** (umockdev-run:2660): DEBUG: 05:02:29.730: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3 (subsystem pci) 330s (umockdev-run:2660): GLib-GIO-DEBUG: 05:02:29.732: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs? 330s (process:2664): libfprint-context-DEBUG: 05:02:29.839: Initializing FpContext (libfprint version 1.94.9+tod1) 330s (process:2664): libfprint-tod-DEBUG: 05:02:29.839: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 330s (process:2664): libfprint-context-DEBUG: 05:02:29.842: No driver found for USB device 1D6B:0002 330s (process:2664): libfprint-device-DEBUG: 05:02:29.842: Device reported probe completion 330s (process:2664): libfprint-device-DEBUG: 05:02:29.842: Completing action FPI_DEVICE_ACTION_PROBE in idle! 330s (process:2664): libfprint-device-DEBUG: 05:02:29.842: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.844: Image device open completed 330s (process:2664): libfprint-device-DEBUG: 05:02:29.844: Device reported open completion 330s (process:2664): libfprint-nb1010-DEBUG: 05:02:29.844: nb1010 Initialized 330s (process:2664): libfprint-device-DEBUG: 05:02:29.844: Completing action FPI_DEVICE_ACTION_OPEN in idle! 330s (process:2664): libfprint-device-DEBUG: 05:02:29.844: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 330s (process:2664): libfprint-device-DEBUG: 05:02:29.844: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.844: Activating image device 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.844: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.844: Image device activation completed 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.844: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.844: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 330s (process:2664): libfprint-SSM-DEBUG: 05:02:29.844: [nb1010] M_LOOP_NUM_STATES entering state 0 330s (process:2664): libfprint-device-DEBUG: 05:02:29.844: Device reported finger status change: FP_FINGER_STATUS_NEEDED 330s (process:2664): libfprint-nb1010-DEBUG: 05:02:29.844: nb1010 Activated 330s (process:2664): libfprint-SSM-DEBUG: 05:02:29.894: [nb1010] M_LOOP_NUM_STATES entering state 1 330s (process:2664): libfprint-SSM-DEBUG: 05:02:29.895: [nb1010] M_LOOP_NUM_STATES entering state 2 330s (process:2664): libfprint-SSM-DEBUG: 05:02:29.896: [nb1010] M_LOOP_NUM_STATES entering state 3 330s (process:2664): libfprint-device-DEBUG: 05:02:29.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.896: Image device reported finger status: on 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.896: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 330s (process:2664): libfprint-SSM-DEBUG: 05:02:29.897: [nb1010] M_LOOP_NUM_STATES entering state 4 330s (process:2664): libfprint-SSM-DEBUG: 05:02:29.898: [nb1010] M_LOOP_NUM_STATES entering state 5 330s (process:2664): libfprint-device-DEBUG: 05:02:29.944: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 330s (process:2664): libfprint-SSM-DEBUG: 05:02:29.945: [nb1010] M_LOOP_NUM_STATES entering state 6 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.945: Image device captured an image 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.945: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 330s (process:2664): libfprint-device-DEBUG: 05:02:29.945: Device reported finger status change: FP_FINGER_STATUS_PRESENT 330s (process:2664): libfprint-SSM-DEBUG: 05:02:29.945: [nb1010] M_LOOP_NUM_STATES completed successfully 330s (process:2664): libfprint-nb1010-DEBUG: 05:02:29.945: nb1010 ssm complete cb 330s (process:2664): libfprint-device-DEBUG: 05:02:29.945: Device reported finger status change: FP_FINGER_STATUS_NONE 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.946: Image device reported finger status: off 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.946: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.946: Deactivating image device 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.946: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.946: Image device deactivation completed 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.946: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 330s (process:2664): libfprint-nb1010-DEBUG: 05:02:29.946: nb1010 Deactivated 330s (process:2664): libfprint-image-DEBUG: 05:02:29.961: Minutiae scan completed in 0.015583 secs 330s (process:2664): libfprint-device-DEBUG: 05:02:29.961: Device reported capture completion 330s (process:2664): libfprint-device-DEBUG: 05:02:29.961: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 330s (process:2664): libfprint-device-DEBUG: 05:02:29.961: Updated temperature model after 0.02 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 330s (process:2664): libfprint-image_device-DEBUG: 05:02:29.962: Image device close completed 330s (process:2664): libfprint-device-DEBUG: 05:02:29.962: Device reported close completion 330s (process:2664): libfprint-nb1010-DEBUG: 05:02:29.962: nb1010 Deinitialized 330s (process:2664): libfprint-device-DEBUG: 05:02:29.962: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 330s (process:2664): libfprint-device-DEBUG: 05:02:29.962: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 331s ** (umockdev-run:2660): DEBUG: 05:02:30.056: umockdev.vala:154: Removing test bed /tmp/umockdev.9FX412 331s (umockdev-run:2660): GLib-DEBUG: 05:02:30.061: unsetenv() is not thread-safe and should not be used after threads are created 331s Comparing PNGs /tmp/libfprint-umockdev-test-m386quhc/capture.png and /usr/share/installed-tests/libfprint-2/nb1010/capture.png 331s PASS: libfprint-2/driver-nb1010.test 331s Running test: libfprint-2/driver-synaptics.test 331s ** (umockdev-run:2673): DEBUG: 05:02:30.142: umockdev.vala:127: Created udev test bed /tmp/umockdev.OMRF22 331s ** (umockdev-run:2673): DEBUG: 05:02:30.142: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9 331s ** (umockdev-run:2673): DEBUG: 05:02:30.143: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb) 331s ** (umockdev-run:2673): DEBUG: 05:02:30.146: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.OMRF22/dev/bus/usb/001/004 331s ** (umockdev-run:2673): DEBUG: 05:02:30.146: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 331s ** (umockdev-run:2673): DEBUG: 05:02:30.147: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 331s ** (umockdev-run:2673): DEBUG: 05:02:30.149: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.OMRF22/dev/bus/usb/001/001 331s ** (umockdev-run:2673): DEBUG: 05:02:30.149: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 331s ** (umockdev-run:2673): DEBUG: 05:02:30.149: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 331s (process:2677): libfprint-context-DEBUG: 05:02:30.250: Initializing FpContext (libfprint version 1.94.9+tod1) 331s (process:2677): libfprint-tod-DEBUG: 05:02:30.250: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 331s (process:2677): libfprint-context-DEBUG: 05:02:30.252: No driver found for USB device 1D6B:0002 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.252: 108170750: ../libfprint/drivers/synaptics/synaptics.c:1247 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.254: Build Time: 1596608839 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.254: Build Num: 3273255 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.254: Version: 10.1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.254: Target: 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.254: Product: 65 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.254: sequence number is 1 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.254: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.255: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.256: Device reported probe completion 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.256: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 331s (process:2677): libfprint-device-DEBUG: 05:02:30.256: Completing action FPI_DEVICE_ACTION_PROBE in idle! 331s (process:2677): libfprint-device-DEBUG: 05:02:30.256: Not updating temperature model, device can run continuously! 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.258: 108176582: ../libfprint/drivers/synaptics/synaptics.c:1407 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.258: sequence number is 2 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.258: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.260: Device reported open completion 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.260: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 331s (process:2677): libfprint-device-DEBUG: 05:02:30.260: Completing action FPI_DEVICE_ACTION_OPEN in idle! 331s (process:2677): libfprint-device-DEBUG: 05:02:30.260: Not updating temperature model, device can run continuously! 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.260: clear all prints in database 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.260: sequence number is 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.260: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.260: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.261: Deleting All Enrolled Users is 0% complete 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.261: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.262: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.262: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.262: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.262: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.262: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.263: Deleting All Enrolled Users is 100% complete 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.263: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.264: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.264: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.264: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.264: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.264: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.265: Successfully deleted all enrolled user 331s (process:2677): libfprint-device-DEBUG: 05:02:30.265: Device reported deletion completion 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.265: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 331s (process:2677): libfprint-device-DEBUG: 05:02:30.265: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 331s (process:2677): libfprint-device-DEBUG: 05:02:30.265: Not updating temperature model, device can run continuously! 331s (process:2677): libfprint-device-DEBUG: 05:02:30.266: Not updating temperature model, device can run continuously! 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.266: 108184506: ../libfprint/drivers/synaptics/synaptics.c:1018 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.266: user_id: FP1-00000000-0-00000000-nobody, finger: 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.266: sequence number is 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.266: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.267: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.267: Device reported finger status change: FP_FINGER_STATUS_NEEDED 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.267: Place Finger on the Sensor! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.267: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.268: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.268: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.269: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.269: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.269: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.269: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.269: Finger is now on the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.269: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.270: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.270: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.270: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.271: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.271: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.271: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.271: Fingerprint image capture complete! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.271: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.272: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.272: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.272: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.272: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.272: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.273: Device reported finger status change: FP_FINGER_STATUS_NEEDED 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.273: Finger is now off the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.273: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.273: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.274: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.274: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.274: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.274: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.274: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.275: Enrollment is 12 % 331s (process:2677): libfprint-device-DEBUG: 05:02:30.275: Device reported enroll progress, reported 1 of 8 have been completed 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.275: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.276: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.276: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.276: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.276: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.276: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.277: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.277: Finger is now on the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.277: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.277: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.277: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.278: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.278: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.278: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.278: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.279: Fingerprint image capture complete! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.279: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.280: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.280: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.281: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.281: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.281: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.281: Device reported finger status change: FP_FINGER_STATUS_NEEDED 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.281: Finger is now off the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.281: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.281: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.282: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.282: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.282: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.283: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.283: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.283: Enrollment is 25 % 331s (process:2677): libfprint-device-DEBUG: 05:02:30.283: Device reported enroll progress, reported 2 of 8 have been completed 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.283: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.284: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.284: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.285: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.285: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.285: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.285: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.285: Finger is now on the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.285: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.285: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.286: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.286: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.286: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.286: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.286: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.287: Fingerprint image capture complete! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.287: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.288: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.288: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.288: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.288: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.288: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.289: Enrollment is 37 % 331s (process:2677): libfprint-device-DEBUG: 05:02:30.289: Device reported enroll progress, reported 3 of 8 have been completed 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.289: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.290: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.290: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.290: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.290: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.290: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.291: Device reported finger status change: FP_FINGER_STATUS_NEEDED 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.291: Finger is now off the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.291: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.291: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.292: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.292: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.292: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.292: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.292: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.293: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.293: Finger is now on the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.293: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.293: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.294: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.294: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.294: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.294: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.294: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.295: Fingerprint image capture complete! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.295: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.295: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.295: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.296: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.296: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.296: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.297: Device reported finger status change: FP_FINGER_STATUS_NEEDED 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.297: Finger is now off the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.297: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.297: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.297: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.297: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.298: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.298: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.298: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.298: Enrollment is 50 % 331s (process:2677): libfprint-device-DEBUG: 05:02:30.298: Device reported enroll progress, reported 4 of 8 have been completed 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.299: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.299: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.299: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.300: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.300: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.300: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.300: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.300: Finger is now on the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.300: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.300: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.301: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.301: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.302: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.302: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.302: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.302: Fingerprint image capture complete! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.302: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.303: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.303: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.303: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.303: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.303: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.304: Device reported finger status change: FP_FINGER_STATUS_NEEDED 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.304: Finger is now off the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.304: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.304: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.305: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.305: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.305: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.305: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.305: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.306: Enrollment is 62 % 331s (process:2677): libfprint-device-DEBUG: 05:02:30.306: Device reported enroll progress, reported 5 of 8 have been completed 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.306: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.306: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.307: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.307: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.307: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.307: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.308: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.308: Finger is now on the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.308: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.308: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.308: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.308: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.309: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.309: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.309: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.309: Fingerprint image capture complete! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.309: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.310: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.310: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.310: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.310: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.310: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.311: Device reported finger status change: FP_FINGER_STATUS_NEEDED 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.311: Finger is now off the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.311: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.311: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.311: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.311: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.312: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.312: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.312: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.312: Enrollment is 62 % 331s (process:2677): libfprint-device-DEBUG: 05:02:30.312: Device reported enroll progress, reported 5 of 8 have been completed 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.312: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.313: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.313: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.314: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.314: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.314: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.315: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.315: Finger is now on the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.315: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.315: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.315: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.315: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.316: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.316: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.316: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.316: Fingerprint image capture complete! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.316: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.317: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.317: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.317: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.317: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.317: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.318: Enrollment is 75 % 331s (process:2677): libfprint-device-DEBUG: 05:02:30.318: Device reported enroll progress, reported 6 of 8 have been completed 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.318: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.319: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.319: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.319: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.319: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.319: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.320: Device reported finger status change: FP_FINGER_STATUS_NEEDED 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.320: Finger is now off the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.320: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.320: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.320: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.320: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.321: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.321: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.321: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.321: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.321: Finger is now on the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.321: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.321: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.322: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.322: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.322: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.322: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.322: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.323: Fingerprint image capture complete! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.323: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.324: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.324: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.324: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.324: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.324: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.325: Device reported finger status change: FP_FINGER_STATUS_NEEDED 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.325: Finger is now off the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.325: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.325: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.325: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.325: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.326: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.326: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.326: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.326: Enrollment is 87 % 331s (process:2677): libfprint-device-DEBUG: 05:02:30.326: Device reported enroll progress, reported 7 of 8 have been completed 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.326: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.327: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.327: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.328: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.328: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.328: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.328: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.328: Finger is now on the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.328: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.328: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.329: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.329: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.329: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.329: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.329: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.330: Fingerprint image capture complete! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.330: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.331: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.331: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.331: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.331: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.331: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.332: Device reported finger status change: FP_FINGER_STATUS_NEEDED 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.332: Finger is now off the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.332: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.332: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.332: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.332: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.333: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.333: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.333: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.334: Enrollment is 100 % 331s (process:2677): libfprint-device-DEBUG: 05:02:30.334: Device reported enroll progress, reported 8 of 8 have been completed 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.334: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.334: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.334: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.335: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.335: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.335: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.336: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.336: Finger is now on the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.336: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.336: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.337: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.337: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.337: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.337: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.337: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.338: Device reported finger status change: FP_FINGER_STATUS_NEEDED 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.338: Finger is now off the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.338: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.338: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.338: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.338: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.339: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.339: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.339: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.339: Enrollment was successful! 331s (process:2677): libfprint-device-DEBUG: 05:02:30.339: Device reported enroll completion 331s (process:2677): libfprint-device-DEBUG: 05:02:30.339: Device reported finger status change: FP_FINGER_STATUS_NONE 331s (process:2677): libfprint-device-DEBUG: 05:02:30.340: Print for finger FP_FINGER_UNKNOWN enrolled 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.340: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 331s (process:2677): libfprint-device-DEBUG: 05:02:30.340: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 331s (process:2677): libfprint-device-DEBUG: 05:02:30.340: Not updating temperature model, device can run continuously! 331s (process:2677): libfprint-device-DEBUG: 05:02:30.340: Not updating temperature model, device can run continuously! 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.340: data is 0x774d0c0 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.340: 108258499: ../libfprint/drivers/synaptics/synaptics.c:650 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.340: sequence number is 5 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.340: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.340: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.341: Device reported finger status change: FP_FINGER_STATUS_NEEDED 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.341: Place Finger on the Sensor! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.341: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.341: got suspend request 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.342: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.342: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 5 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.342: got resume request 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.342: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 6 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.342: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.344: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.344: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.344: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.344: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.344: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.345: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.345: Finger is now on the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.345: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.345: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.346: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.346: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.346: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.346: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.346: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.347: Fingerprint image capture complete! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.347: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.348: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.348: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.348: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.348: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.348: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-device-DEBUG: 05:02:30.349: Device reported finger status change: FP_FINGER_STATUS_NEEDED 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.349: Finger is now off the sensor 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.349: Received message with 0 sequence number 0x91, ignoring! 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.349: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.349: interrupt transfer done 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.349: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.350: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.350: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.350: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.351: Verify was successful! for user: FP1-00000000-0-00000000-nobody finger: 1 score: 61.800000 331s (process:2677): libfprint-device-DEBUG: 05:02:30.351: Device reported verify result 331s (process:2677): libfprint-device-DEBUG: 05:02:30.351: Device reported verify completion 331s (process:2677): libfprint-device-DEBUG: 05:02:30.351: Device reported finger status change: FP_FINGER_STATUS_NONE 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.351: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 331s (process:2677): libfprint-device-DEBUG: 05:02:30.351: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 331s (process:2677): libfprint-device-DEBUG: 05:02:30.351: Not updating temperature model, device can run continuously! 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.351: data is 0x774d0c0 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.351: 108269587: ../libfprint/drivers/synaptics/synaptics.c:1127 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.351: sequence number is 6 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.351: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.351: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.352: Successfully deleted enrolled user 331s (process:2677): libfprint-device-DEBUG: 05:02:30.352: Device reported deletion completion 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.352: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 331s (process:2677): libfprint-device-DEBUG: 05:02:30.352: Completing action FPI_DEVICE_ACTION_DELETE in idle! 331s (process:2677): libfprint-device-DEBUG: 05:02:30.352: Not updating temperature model, device can run continuously! 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.352: 108270782: ../libfprint/drivers/synaptics/synaptics.c:1428 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.352: sequence number is 7 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.352: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.353: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1 331s (process:2677): libfprint-synaptics-DEBUG: 05:02:30.353: Fingerprint sensor ready to be powered down 331s (process:2677): libfprint-device-DEBUG: 05:02:30.353: Device reported close completion 331s (process:2677): libfprint-SSM-DEBUG: 05:02:30.354: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully 331s (process:2677): libfprint-device-DEBUG: 05:02:30.354: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 331s (process:2677): libfprint-device-DEBUG: 05:02:30.354: Not updating temperature model, device can run continuously! 331s enrolling 331s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfd0a72c1de40 (FpiDeviceSynaptics at 0x7750bb0)>, 1, None, None, None) 331s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfd0a72c1de40 (FpiDeviceSynaptics at 0x7750bb0)>, 2, None, None, None) 331s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfd0a72c1de40 (FpiDeviceSynaptics at 0x7750bb0)>, 3, None, None, None) 331s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfd0a72c1de40 (FpiDeviceSynaptics at 0x7750bb0)>, 4, None, None, None) 331s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfd0a72c1de40 (FpiDeviceSynaptics at 0x7750bb0)>, 5, None, None, None) 331s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfd0a72c1de40 (FpiDeviceSynaptics at 0x7750bb0)>, 5, None, None, GLib.Error('Please try again.', 'fp - device - retry - quark', 0)) 331s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfd0a72c1de40 (FpiDeviceSynaptics at 0x7750bb0)>, 6, None, None, None) 331s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfd0a72c1de40 (FpiDeviceSynaptics at 0x7750bb0)>, 7, None, None, None) 331s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0xfd0a72c1de40 (FpiDeviceSynaptics at 0x7750bb0)>, 8, None, None, None) 331s enroll done 331s verifying 331s verify done 331s deleting 331s delete done 331s libusb: warning [libusb_exit] device 1.1 still referenced 331s ** (umockdev-run:2673): DEBUG: 05:02:30.387: umockdev.vala:154: Removing test bed /tmp/umockdev.OMRF22 331s (umockdev-run:2673): GLib-DEBUG: 05:02:30.390: unsetenv() is not thread-safe and should not be used after threads are created 331s PASS: libfprint-2/driver-synaptics.test 331s Running test: libfprint-2/driver-fpcmoc.test 332s ** (umockdev-run:2685): DEBUG: 05:02:30.452: umockdev.vala:127: Created udev test bed /tmp/umockdev.10SL22 332s ** (umockdev-run:2685): DEBUG: 05:02:30.452: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-1 332s ** (umockdev-run:2685): DEBUG: 05:02:30.454: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-1 (subsystem usb) 332s ** (umockdev-run:2685): DEBUG: 05:02:30.456: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.10SL22/dev/bus/usb/001/019 332s ** (umockdev-run:2685): DEBUG: 05:02:30.456: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 332s ** (umockdev-run:2685): DEBUG: 05:02:30.457: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 332s ** (umockdev-run:2685): DEBUG: 05:02:30.459: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.10SL22/dev/bus/usb/001/001 332s ** (umockdev-run:2685): DEBUG: 05:02:30.459: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 332s ** (umockdev-run:2685): DEBUG: 05:02:30.460: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 332s (process:2689): libfprint-context-DEBUG: 05:02:30.562: Initializing FpContext (libfprint version 1.94.9+tod1) 332s (process:2689): libfprint-tod-DEBUG: 05:02:30.563: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 332s (process:2689): libfprint-DEBUG: 05:02:30.564: fpi_device_fpcmoc_init enter --> 332s (process:2689): libfprint-DEBUG: 05:02:30.564: 108483128: ../libfprint/drivers/fpcmoc/fpc.c:1875 332s (process:2689): libfprint-context-DEBUG: 05:02:30.565: No driver found for USB device 1D6B:0002 332s (process:2689): libfprint-DEBUG: 05:02:30.565: fpc_dev_probe enter --> 332s (process:2689): libfprint-DEBUG: 05:02:30.568: Device name: FPC L:0001 FW:127010 332s (process:2689): libfprint-device-DEBUG: 05:02:30.568: Device reported probe completion 332s (process:2689): libfprint-device-DEBUG: 05:02:30.568: Completing action FPI_DEVICE_ACTION_PROBE in idle! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.568: Not updating temperature model, device can run continuously! 332s (process:2689): libfprint-DEBUG: 05:02:30.569: fpc_dev_open enter --> 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.570: [fpcmoc] FP_INIT_NUM_STATES entering state 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.570: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.570: fpc_send_ctrl_cmd CMD: 0x1, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-DEBUG: 05:02:30.571: fpc_cmd_receive_cb current ssm request: 1 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.571: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.571: fpc_cmd_receive_cb current ssm request: 1 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.571: fpc_cmd_receive_cb recv evt data length: 38 332s (process:2689): libfprint-DEBUG: 05:02:30.571: fpc_evt_cb INIT: status=0, Sensor = 1523, HWID = 0x1711, WxH = 96 x 96 332s (process:2689): libfprint-DEBUG: 05:02:30.571: fpc_evt_cb INIT: FW version: 1.27.0.10 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.571: [fpcmoc] FP_INIT_NUM_STATES entering state 1 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.571: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.571: fpc_send_ctrl_cmd CMD: 0x60, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.572: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.572: fpc_cmd_receive_cb current ssm request: 96 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.572: fpc_init_load_db_cb got dbid size: 16 332s (process:2689): libfprint-DEBUG: 05:02:30.572: fpc_init_load_db_cb dbid: 0xa981b581-adfc-e643-a0d0-88c2138092f7 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.572: [fpcmoc] FP_INIT_NUM_STATES completed successfully 332s (process:2689): libfprint-device-DEBUG: 05:02:30.572: Device reported open completion 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.572: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-device-DEBUG: 05:02:30.572: Completing action FPI_DEVICE_ACTION_OPEN in idle! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.572: Not updating temperature model, device can run continuously! 332s (process:2689): libfprint-DEBUG: 05:02:30.572: fpc_dev_clear_storage enter --> 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.572: [fpcmoc] Clear storage entering state 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.572: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.572: fpc_send_ctrl_cmd CMD: 0x62, value: 0x0, index: 0 type: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.573: fpc_cmd_receive_cb current ssm request: 98 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.573: [fpcmoc] Clear storage entering state 1 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.573: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.573: fpc_send_ctrl_cmd CMD: 0x60, value: 0x1, index: 0 type: 1 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.573: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.573: fpc_cmd_receive_cb current ssm request: 96 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.573: [fpcmoc] Clear storage completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.573: Clear Storage complete! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.573: Device reported deletion completion 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.573: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-device-DEBUG: 05:02:30.573: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.573: Not updating temperature model, device can run continuously! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.574: Not updating temperature model, device can run continuously! 332s (process:2689): libfprint-DEBUG: 05:02:30.574: fpc_dev_enroll enter --> 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.574: [fpcmoc] enroll entering state 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.574: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.574: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-DEBUG: 05:02:30.575: fpc_cmd_receive_cb current ssm request: 112 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.575: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.576: fpc_cmd_receive_cb current ssm request: 112 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.576: fpc_cmd_receive_cb recv evt data length: 790 332s (process:2689): libfprint-DEBUG: 05:02:30.576: fpc_evt_cb Enum Fids: status = 0, NumFids = 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.576: [fpcmoc] enroll entering state 1 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.576: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.576: fpc_send_ctrl_cmd CMD: 0x67, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.576: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.576: fpc_cmd_receive_cb current ssm request: 103 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.576: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-device-DEBUG: 05:02:30.576: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.576: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.576: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.576: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.577: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.577: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.577: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.577: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.577: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.577: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.577: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.577: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.577: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.578: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.578: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.578: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.579: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.579: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.579: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.579: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.579: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.579: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.579: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.579: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.580: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.580: Enrol Update status: 1, remaining: 11 332s (process:2689): libfprint-device-DEBUG: 05:02:30.580: Device reported enroll progress, reported 1 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.580: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.580: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.580: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.580: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.580: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.580: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.581: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.581: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.581: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.581: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.581: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.581: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.581: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.581: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.581: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.581: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.582: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.582: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.582: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.582: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.582: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.582: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.582: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.583: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.583: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.583: Enrol Update status: 1, remaining: 10 332s (process:2689): libfprint-device-DEBUG: 05:02:30.583: Device reported enroll progress, reported 2 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.583: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.583: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.583: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.583: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.583: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.583: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.584: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.584: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.584: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.584: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.584: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.584: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.584: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.584: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.584: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.584: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.585: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.585: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.585: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.585: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.585: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.585: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.585: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.585: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.585: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.585: Enrol Update status: 1, remaining: 9 332s (process:2689): libfprint-device-DEBUG: 05:02:30.585: Device reported enroll progress, reported 3 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.586: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.586: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.586: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.586: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.586: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.586: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.587: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.587: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.587: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.587: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.587: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.587: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.587: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.587: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.588: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.588: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.588: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.588: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.588: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.588: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.588: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.588: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.588: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.588: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.589: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.589: Enrol Update status: 1, remaining: 8 332s (process:2689): libfprint-device-DEBUG: 05:02:30.589: Device reported enroll progress, reported 4 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.589: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.589: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.589: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.589: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.589: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.589: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.590: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.590: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.590: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.590: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.590: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.590: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.590: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.590: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.591: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.591: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.591: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.591: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.591: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.591: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.591: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.591: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.591: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.591: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.592: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.592: Enrol Update status: 1, remaining: 7 332s (process:2689): libfprint-device-DEBUG: 05:02:30.592: Device reported enroll progress, reported 5 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.592: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.592: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.592: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.592: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.592: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.592: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.593: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.593: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.593: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.593: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.593: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.593: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.593: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.593: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.594: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.594: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.594: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.594: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.594: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.594: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.594: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.594: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.594: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.594: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.595: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.595: Enrol Update status: 5, remaining: 7 332s (process:2689): libfprint-DEBUG: 05:02:30.595: Sample overlapping ratio is too High 332s (process:2689): libfprint-device-DEBUG: 05:02:30.595: Device reported enroll progress, reported 5 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.595: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.595: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.595: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.595: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.595: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.595: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.596: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.596: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.596: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.596: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.596: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.596: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.596: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.596: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.596: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.597: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.597: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.597: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.597: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.597: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.597: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.597: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.597: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.597: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.598: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.598: Enrol Update status: 1, remaining: 6 332s (process:2689): libfprint-device-DEBUG: 05:02:30.598: Device reported enroll progress, reported 6 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.598: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.598: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.598: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.598: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.598: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.598: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.599: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.599: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.599: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.599: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.599: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.599: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.599: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.600: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.600: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.600: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.600: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.600: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.600: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.600: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.600: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.600: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.600: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.601: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.601: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.601: Enrol Update status: 1, remaining: 5 332s (process:2689): libfprint-device-DEBUG: 05:02:30.601: Device reported enroll progress, reported 7 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.601: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.601: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.601: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.601: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.601: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.601: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.602: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.602: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.602: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.602: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.602: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.602: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.602: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.602: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.602: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.602: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.603: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.603: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.603: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.603: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.603: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.603: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.603: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.603: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.604: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.604: Enrol Update status: 5, remaining: 5 332s (process:2689): libfprint-DEBUG: 05:02:30.604: Sample overlapping ratio is too High 332s (process:2689): libfprint-device-DEBUG: 05:02:30.604: Device reported enroll progress, reported 7 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.604: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.604: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.604: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.604: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.605: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.605: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.605: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.605: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.605: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.605: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.605: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.605: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.605: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.605: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.606: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.606: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.606: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.606: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.606: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.606: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.606: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.606: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.607: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.607: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.607: Enrol Update status: 1, remaining: 4 332s (process:2689): libfprint-device-DEBUG: 05:02:30.607: Device reported enroll progress, reported 8 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.607: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.607: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.607: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.607: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.608: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.608: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.608: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.608: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.608: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.608: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.608: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.608: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.608: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.609: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.609: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.609: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.609: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.609: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.609: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.609: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.609: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.609: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.609: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.610: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.610: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.610: Enrol Update status: 1, remaining: 3 332s (process:2689): libfprint-device-DEBUG: 05:02:30.610: Device reported enroll progress, reported 9 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.611: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.611: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.611: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.611: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.611: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.611: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.612: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.612: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.612: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.612: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.612: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.612: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.612: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.612: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.612: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.612: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.613: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.613: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.613: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.613: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.613: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.613: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.613: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.613: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.613: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.613: Enrol Update status: 1, remaining: 2 332s (process:2689): libfprint-device-DEBUG: 05:02:30.613: Device reported enroll progress, reported 10 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.613: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.613: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.613: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.614: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.614: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.614: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.614: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.614: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.614: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.614: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.614: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.614: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.614: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.614: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.615: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.615: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.615: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.615: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.615: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.615: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.615: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.615: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.615: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.615: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.615: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.616: Enrol Update status: 5, remaining: 2 332s (process:2689): libfprint-DEBUG: 05:02:30.616: Sample overlapping ratio is too High 332s (process:2689): libfprint-device-DEBUG: 05:02:30.616: Device reported enroll progress, reported 10 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.616: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.616: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.616: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.616: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.616: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.616: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.617: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.617: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.617: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.617: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.617: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.617: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.617: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.617: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.617: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.617: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.618: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.618: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.618: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.618: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.618: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.618: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.618: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.618: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.618: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.618: Enrol Update status: 1, remaining: 1 332s (process:2689): libfprint-device-DEBUG: 05:02:30.618: Device reported enroll progress, reported 11 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.618: [fpcmoc] enroll entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.618: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.618: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.619: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.619: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.619: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.619: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.619: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.619: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.619: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.619: [fpcmoc] enroll entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.619: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.619: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.619: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.620: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.620: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.620: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.620: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.620: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.620: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.620: [fpcmoc] enroll entering state 4 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.620: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.620: fpc_send_ctrl_cmd CMD: 0x68, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.620: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.620: fpc_cmd_receive_cb current ssm request: 104 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.620: Enrol Update status: 0, remaining: 0 332s (process:2689): libfprint-device-DEBUG: 05:02:30.620: Device reported enroll progress, reported 12 of 25 have been completed 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.620: [fpcmoc] enroll entering state 5 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.620: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.620: fpc_send_ctrl_cmd CMD: 0x69, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.621: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.621: fpc_cmd_receive_cb current ssm request: 105 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.621: Enrol End status: 0, fid: 0x0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.621: [fpcmoc] enroll entering state 6 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.621: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.621: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.621: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.621: fpc_cmd_receive_cb current ssm request: 107 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.621: [fpcmoc] enroll entering state 7 332s (process:2689): libfprint-DEBUG: 05:02:30.621: user_id: FP1-00000000-0-00000000-nobody, finger: 0xf5 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.621: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.621: fpc_send_ctrl_cmd CMD: 0x6a, value: 0x0, index: 0 type: 1 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.622: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.622: fpc_cmd_receive_cb current ssm request: 106 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.622: [fpcmoc] enroll entering state 8 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.622: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.622: fpc_send_ctrl_cmd CMD: 0x61, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.622: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.623: fpc_cmd_receive_cb current ssm request: 97 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.623: [fpcmoc] enroll entering state 9 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.623: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.623: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.623: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.623: fpc_cmd_receive_cb current ssm request: 3 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.623: fpc_do_abort_cb Do abort for reasons 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.623: [fpcmoc] enroll entering state 10 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.623: [fpcmoc] enroll completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.623: Enrollment complete! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.623: Device reported enroll completion 332s (process:2689): libfprint-device-DEBUG: 05:02:30.623: Device reported finger status change: FP_FINGER_STATUS_NONE 332s (process:2689): libfprint-device-DEBUG: 05:02:30.623: Print for finger FP_FINGER_UNKNOWN enrolled 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.623: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-device-DEBUG: 05:02:30.623: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.623: Not updating temperature model, device can run continuously! 332s (process:2689): libfprint-DEBUG: 05:02:30.623: fpc_dev_template_list enter --> 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.623: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.623: fpc_send_ctrl_cmd CMD: 0x70, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-DEBUG: 05:02:30.624: fpc_cmd_receive_cb current ssm request: 112 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.624: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.624: fpc_cmd_receive_cb current ssm request: 112 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.624: fpc_cmd_receive_cb recv evt data length: 790 332s (process:2689): libfprint-DEBUG: 05:02:30.624: Query templates complete! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.624: Device reported listing completion 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.624: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-device-DEBUG: 05:02:30.624: Completing action FPI_DEVICE_ACTION_LIST in idle! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.624: Not updating temperature model, device can run continuously! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.625: Not updating temperature model, device can run continuously! 332s (process:2689): libfprint-DEBUG: 05:02:30.625: fpc_dev_verify_identify enter --> 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.625: [fpcmoc] verify_identify entering state 0 332s (process:2689): libfprint-device-DEBUG: 05:02:30.625: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.625: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.625: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-DEBUG: 05:02:30.625: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.625: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.626: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.626: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.626: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.626: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.626: [fpcmoc] verify_identify entering state 1 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.626: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.626: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.626: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.626: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.627: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.627: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.627: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.627: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.627: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.627: [fpcmoc] verify_identify entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.627: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.627: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.627: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.627: fpc_cmd_receive_cb current ssm request: 107 state: 0 332s (process:2689): libfprint-device-DEBUG: 05:02:30.628: Device reported verify result 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.628: [fpcmoc] verify_identify entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.628: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.628: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.628: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.628: fpc_cmd_receive_cb current ssm request: 3 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.628: fpc_do_abort_cb Do abort for reasons 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.628: [fpcmoc] verify_identify completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.628: Verify_identify complete! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.628: Device reported verify completion 332s (process:2689): libfprint-device-DEBUG: 05:02:30.628: Device reported finger status change: FP_FINGER_STATUS_NONE 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.628: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-device-DEBUG: 05:02:30.628: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.628: Not updating temperature model, device can run continuously! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.629: Not updating temperature model, device can run continuously! 332s (process:2689): libfprint-DEBUG: 05:02:30.629: fpc_dev_verify_identify enter --> 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.629: [fpcmoc] verify_identify entering state 0 332s (process:2689): libfprint-device-DEBUG: 05:02:30.629: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.629: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.629: fpc_send_ctrl_cmd CMD: 0x2, value: 0x1, index: 0 type: 2 332s (process:2689): libfprint-DEBUG: 05:02:30.629: fpc_cmd_receive_cb current ssm request: 2 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.629: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.630: fpc_cmd_receive_cb current ssm request: 2 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.630: fpc_cmd_receive_cb recv evt data length: 12 332s (process:2689): libfprint-DEBUG: 05:02:30.630: fpc_evt_cb Got finger down event (0) 332s (process:2689): libfprint-device-DEBUG: 05:02:30.630: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.630: [fpcmoc] verify_identify entering state 1 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.630: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.630: fpc_send_ctrl_cmd CMD: 0x9, value: 0x0, index: 0 type: 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.630: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.631: fpc_cmd_receive_cb current ssm request: 9 state: 0 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.631: [fpcmoc] FP_CMD_NUM_STATES entering state 1 332s (process:2689): libfprint-DEBUG: 05:02:30.631: fpc_cmd_receive_cb current ssm request: 9 state: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.631: fpc_cmd_receive_cb recv evt data length: 24 332s (process:2689): libfprint-DEBUG: 05:02:30.631: fpc_evt_cb Got capture event 332s (process:2689): libfprint-device-DEBUG: 05:02:30.631: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.631: [fpcmoc] verify_identify entering state 2 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.631: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.631: fpc_send_ctrl_cmd CMD: 0x6b, value: 0x0, index: 0 type: 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.631: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.632: fpc_cmd_receive_cb current ssm request: 107 state: 0 332s (process:2689): libfprint-device-DEBUG: 05:02:30.632: Device reported identify result 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.632: [fpcmoc] verify_identify entering state 3 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.632: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.632: fpc_send_ctrl_cmd CMD: 0x3, value: 0x1, index: 0 type: 1 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.632: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.632: fpc_cmd_receive_cb current ssm request: 3 state: 0 332s (process:2689): libfprint-DEBUG: 05:02:30.632: fpc_do_abort_cb Do abort for reasons 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.632: [fpcmoc] verify_identify completed successfully 332s (process:2689): libfprint-DEBUG: 05:02:30.632: Verify_identify complete! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.632: Device reported identify completion 332s (process:2689): libfprint-device-DEBUG: 05:02:30.632: Device reported finger status change: FP_FINGER_STATUS_NONE 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.632: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-device-DEBUG: 05:02:30.632: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.632: Not updating temperature model, device can run continuously! 332s (process:2689): libfprint-DEBUG: 05:02:30.633: fpc_dev_template_delete enter --> 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.633: [fpcmoc] FP_CMD_NUM_STATES entering state 0 332s (process:2689): libfprint-DEBUG: 05:02:30.633: fpc_send_ctrl_cmd CMD: 0x63, value: 0x0, index: 0 type: 1 332s (process:2689): libfprint-DEBUG: 05:02:30.633: fpc_dev_template_delete exit <-- 332s (process:2689): libfprint-DEBUG: 05:02:30.633: fpc_cmd_receive_cb current ssm request: 99 state: 0 332s (process:2689): libfprint-device-DEBUG: 05:02:30.633: Device reported deletion completion 332s (process:2689): libfprint-SSM-DEBUG: 05:02:30.633: [fpcmoc] FP_CMD_NUM_STATES completed successfully 332s (process:2689): libfprint-device-DEBUG: 05:02:30.633: Completing action FPI_DEVICE_ACTION_DELETE in idle! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.633: Not updating temperature model, device can run continuously! 332s (process:2689): libfprint-DEBUG: 05:02:30.633: fpc_dev_close enter --> 332s (process:2689): libfprint-device-DEBUG: 05:02:30.634: Device reported close completion 332s (process:2689): libfprint-device-DEBUG: 05:02:30.634: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 332s (process:2689): libfprint-device-DEBUG: 05:02:30.634: Not updating temperature model, device can run continuously! 332s Clear 332s Clear done 332s enrolling 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 1, None, None, None) 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 2, None, None, None) 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 3, None, None, None) 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 4, None, None, None) 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 5, None, None, None) 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 5, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 6, None, None, None) 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 7, None, None, None) 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 7, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 8, None, None, None) 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 9, None, None, None) 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 10, None, None, None) 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 10, None, None, GLib.Error('Please try again after removing the finger first.', 'fp - device - retry - quark', 3)) 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 11, None, None, None) 332s enroll progress: (<__gi__.FpiDeviceFpcMoc object at 0xf0fae04fdf40 (FpiDeviceFpcMoc at 0x177cca20)>, 12, None, None, None) 332s enroll done 332s listing 332s listing done 332s verifying 332s verify done 332s async identifying 332s indentification_done: 332s deleting 332s delete done 332s ** (umockdev-run:2685): DEBUG: 05:02:30.668: umockdev.vala:154: Removing test bed /tmp/umockdev.10SL22 332s (umockdev-run:2685): GLib-DEBUG: 05:02:30.672: unsetenv() is not thread-safe and should not be used after threads are created 332s PASS: libfprint-2/driver-fpcmoc.test 332s Running test: libfprint-2/driver-uru4000-msv2.test 332s ** (umockdev-run:2697): DEBUG: 05:02:30.733: umockdev.vala:127: Created udev test bed /tmp/umockdev.BB5212 332s ** (umockdev-run:2697): DEBUG: 05:02:30.733: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-10 332s ** (umockdev-run:2697): DEBUG: 05:02:30.734: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-10 (subsystem usb) 332s ** (umockdev-run:2697): DEBUG: 05:02:30.736: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.BB5212/dev/bus/usb/001/047 332s ** (umockdev-run:2697): DEBUG: 05:02:30.736: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 332s ** (umockdev-run:2697): DEBUG: 05:02:30.737: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 332s ** (umockdev-run:2697): DEBUG: 05:02:30.739: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.BB5212/dev/bus/usb/001/001 332s ** (umockdev-run:2697): DEBUG: 05:02:30.739: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 332s ** (umockdev-run:2697): DEBUG: 05:02:30.739: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 332s (process:2701): libfprint-context-DEBUG: 05:02:30.873: Initializing FpContext (libfprint version 1.94.9+tod1) 332s (process:2701): libfprint-tod-DEBUG: 05:02:30.873: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 332s (process:2701): libfprint-context-DEBUG: 05:02:30.876: No driver found for USB device 1D6B:0002 332s (process:2701): libfprint-device-DEBUG: 05:02:30.876: Device reported probe completion 332s (process:2701): libfprint-device-DEBUG: 05:02:30.876: Completing action FPI_DEVICE_ACTION_PROBE in idle! 332s (process:2701): libfprint-device-DEBUG: 05:02:30.876: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.880: Image device open completed 332s (process:2701): libfprint-device-DEBUG: 05:02:30.880: Device reported open completion 332s (process:2701): libfprint-device-DEBUG: 05:02:30.880: Completing action FPI_DEVICE_ACTION_OPEN in idle! 332s (process:2701): libfprint-device-DEBUG: 05:02:30.880: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 332s (process:2701): libfprint-device-DEBUG: 05:02:30.880: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.880: Activating image device 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.880: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.881: [uru4000] INIT_NUM_STATES entering state 0 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.881: read 1 regs at 7 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.882: reg value 3 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.882: [uru4000] INIT_NUM_STATES entering state 1 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.882: [uru4000] INIT_NUM_STATES entering state 3 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.882: set 83 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.882: [uru4000] INIT_NUM_STATES entering state 4 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.882: [uru4000] POWERUP_NUM_STATES entering state 0 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.882: [uru4000] POWERUP_NUM_STATES entering state 1 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.882: set 03 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.883: [uru4000] POWERUP_NUM_STATES entering state 2 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.883: read 1 regs at 7 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.884: reg value 83 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.884: [uru4000] POWERUP_NUM_STATES entering state 3 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.884: [uru4000] POWERUP_NUM_STATES entering state 4 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.894: [uru4000] POWERUP_NUM_STATES entering state 5 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.894: 108812577: ../libfprint/drivers/uru4000.c:326 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.895: [uru4000] POWERUP_NUM_STATES entering state 6 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.895: [uru4000] POWERUP_NUM_STATES entering state 1 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.895: set 03 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.896: [uru4000] POWERUP_NUM_STATES entering state 2 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.896: read 1 regs at 7 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.897: reg value 3 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.897: [uru4000] POWERUP_NUM_STATES entering state 3 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.897: [uru4000] POWERUP_NUM_STATES completed successfully 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.897: [uru4000] INIT_NUM_STATES entering state 5 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.897: recv irq type 56aa 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.897: late scanpwr interrupt 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.898: [uru4000] INIT_NUM_STATES entering state 6 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.898: [uru4000] INIT_NUM_STATES entering state 7 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.898: read 16 regs at f0 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.899: reg value 50 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.899: [uru4000] INIT_NUM_STATES entering state 8 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.899: Versions 0059 and 0034 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.899: [uru4000] INIT_NUM_STATES completed successfully 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.899: Image device activation completed 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.899: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.899: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.899: wait finger on 332s (process:2701): libfprint-device-DEBUG: 05:02:30.899: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.900: recv irq type 0101 332s (process:2701): libfprint-device-DEBUG: 05:02:30.900: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.900: Image device reported finger status: on 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.900: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.900: starting capture 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.900: Image encryption seed: 1374298404 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.900: [uru4000] IMAGING_NUM_STATES entering state 0 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.902: [uru4000] IMAGING_NUM_STATES entering state 1 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.902: hw header lines 289 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.902: dev2: 10849 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.902: image seems to be encrypted 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.903: [uru4000] IMAGING_NUM_STATES entering state 2 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.903: read 4 regs at 34 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.903: reg value 7b 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.904: [uru4000] IMAGING_NUM_STATES entering state 3 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: encryption id 05 -> key db896f5f 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: 0 02 67 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: decoding 67 lines 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: 1 00 1 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: skipping 1 lines 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: 2 02 49 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: decoding 49 lines 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: 3 01 1 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: skipping 1 lines 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: 4 00 1 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: skipping 1 lines 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: 5 02 49 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: decoding 49 lines 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: 6 00 1 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: skipping 1 lines 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: 7 02 121 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.904: decoding 121 lines 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.904: [uru4000] IMAGING_NUM_STATES entering state 4 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.904: Image device captured an image 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.905: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 332s (process:2701): libfprint-device-DEBUG: 05:02:30.906: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2701): libfprint-SSM-DEBUG: 05:02:30.906: [uru4000] IMAGING_NUM_STATES completed successfully 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.906: await finger off 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.908: recv irq type 0200 332s (process:2701): libfprint-device-DEBUG: 05:02:30.908: Device reported finger status change: FP_FINGER_STATUS_NONE 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.908: Image device reported finger status: off 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.908: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.908: Deactivating image device 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.908: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.908: deactivating 332s (process:2701): libfprint-uru4000-DEBUG: 05:02:30.908: cancelled 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.908: Image device deactivation completed 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.908: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 332s (process:2701): libfprint-image-DEBUG: 05:02:30.948: Minutiae scan completed in 0.043442 secs 332s (process:2701): libfprint-device-DEBUG: 05:02:30.948: Device reported capture completion 332s (process:2701): libfprint-device-DEBUG: 05:02:30.949: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 332s (process:2701): libfprint-device-DEBUG: 05:02:30.949: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 332s (process:2701): libfprint-image_device-DEBUG: 05:02:30.949: Image device close completed 332s (process:2701): libfprint-device-DEBUG: 05:02:30.949: Device reported close completion 332s (process:2701): libfprint-device-DEBUG: 05:02:30.949: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 332s (process:2701): libfprint-device-DEBUG: 05:02:30.950: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s ** (umockdev-run:2697): DEBUG: 05:02:31.175: umockdev.vala:154: Removing test bed /tmp/umockdev.BB5212 332s (umockdev-run:2697): GLib-DEBUG: 05:02:31.182: unsetenv() is not thread-safe and should not be used after threads are created 332s Comparing PNGs /tmp/libfprint-umockdev-test-hqm3ft7a/capture.png and /usr/share/installed-tests/libfprint-2/uru4000-msv2/capture.png 332s PASS: libfprint-2/driver-uru4000-msv2.test 332s Running test: libfprint-2/driver-egismoc-05a1.test 332s ** (umockdev-run:2710): DEBUG: 05:02:31.304: umockdev.vala:127: Created udev test bed /tmp/umockdev.C5AJ22 332s ** (umockdev-run:2710): DEBUG: 05:02:31.304: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-5 332s ** (umockdev-run:2710): DEBUG: 05:02:31.306: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-5 (subsystem usb) 332s ** (umockdev-run:2710): DEBUG: 05:02:31.309: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.C5AJ22/dev/bus/usb/001/003 332s ** (umockdev-run:2710): DEBUG: 05:02:31.309: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1 332s ** (umockdev-run:2710): DEBUG: 05:02:31.310: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb) 332s ** (umockdev-run:2710): DEBUG: 05:02:31.312: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.C5AJ22/dev/bus/usb/001/001 332s ** (umockdev-run:2710): DEBUG: 05:02:31.312: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0 332s ** (umockdev-run:2710): DEBUG: 05:02:31.312: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci) 332s (process:2714): libfprint-context-DEBUG: 05:02:31.416: Initializing FpContext (libfprint version 1.94.9+tod1) 332s (process:2714): libfprint-tod-DEBUG: 05:02:31.416: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.418: 109336943: ../libfprint/drivers/egismoc/egismoc.c:1597 332s (process:2714): libfprint-context-DEBUG: 05:02:31.419: No driver found for USB device 1D6B:0002 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.419: egismoc_probe enter --> 332s (process:2714): libfprint-device-DEBUG: 05:02:31.420: Device reported probe completion 332s (process:2714): libfprint-device-DEBUG: 05:02:31.420: Completing action FPI_DEVICE_ACTION_PROBE in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.420: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.422: Opening device 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.422: [egismoc] DEV_INIT_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.427: [egismoc] DEV_INIT_STATES entering state 1 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.428: [egismoc] DEV_INIT_STATES entering state 2 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.429: [egismoc] DEV_INIT_STATES entering state 3 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.429: [egismoc] DEV_INIT_STATES entering state 4 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.430: [egismoc] DEV_INIT_STATES entering state 5 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.430: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.430: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.430: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.431: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.432: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.432: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.432: Firmware version callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.432: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.432: Device firmware version is 9050.1.2.13 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.432: [egismoc] DEV_INIT_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.432: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.432: Device reported open completion 332s (process:2714): libfprint-device-DEBUG: 05:02:31.432: Completing action FPI_DEVICE_ACTION_OPEN in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.432: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.433: List 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.433: [egismoc] LIST_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.433: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.433: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.433: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.433: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.434: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.434: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.434: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.434: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.434: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.434: Device fingerprint 3: FP1-20231209-2-04EFB67C-root 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.434: Number of currently enrolled fingerprints on the device is 3 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.434: [egismoc] LIST_STATES entering state 1 332s (process:2714): libfprint-device-DEBUG: 05:02:31.434: Device reported listing completion 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.434: [egismoc] LIST_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.434: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.434: Completing action FPI_DEVICE_ACTION_LIST in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.434: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.434: Clear storage 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.434: [egismoc] DELETE_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.434: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.434: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.434: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.435: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.436: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.436: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.436: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.436: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.436: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.436: Device fingerprint 3: FP1-20231209-2-04EFB67C-root 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.436: Number of currently enrolled fingerprints on the device is 3 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.436: [egismoc] DELETE_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.436: Get delete command 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.436: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.436: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.436: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.437: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.438: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.438: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.438: Delete callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.438: Response prefix valid: yes 332s (process:2714): libfprint-device-DEBUG: 05:02:31.438: Device reported deletion completion 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.438: [egismoc] DELETE_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.438: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.438: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.438: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.438: List 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.438: [egismoc] LIST_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.438: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.438: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.438: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.438: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.439: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.439: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.439: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.439: Number of currently enrolled fingerprints on the device is 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.439: [egismoc] LIST_STATES entering state 1 332s (process:2714): libfprint-device-DEBUG: 05:02:31.439: Device reported listing completion 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.439: [egismoc] LIST_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.439: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.439: Completing action FPI_DEVICE_ACTION_LIST in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.439: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 332s (process:2714): libfprint-device-DEBUG: 05:02:31.440: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.440: Enroll 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.440: [egismoc] ENROLL_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.440: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.440: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.440: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.440: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.441: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.441: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.441: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.441: Number of currently enrolled fingerprints on the device is 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.441: [egismoc] ENROLL_STATES entering state 1 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.441: [egismoc] ENROLL_STATES entering state 2 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.441: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.441: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.441: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.442: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.442: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.442: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.442: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.442: [egismoc] ENROLL_STATES entering state 3 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.442: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.442: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.442: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.443: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.443: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.443: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.443: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.443: [egismoc] ENROLL_STATES entering state 4 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.443: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.443: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.444: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.444: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.444: [egismoc] ENROLL_STATES entering state 5 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.444: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.444: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.444: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.444: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.445: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.445: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.445: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.445: [egismoc] ENROLL_STATES entering state 6 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.445: Get check command 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.445: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.445: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.445: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.445: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.446: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.446: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.446: Enroll check callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.446: Response suffix valid: yes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.446: [egismoc] ENROLL_STATES entering state 7 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.446: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.446: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.446: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.447: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.447: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.447: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.447: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.447: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.447: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.447: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.447: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.448: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.448: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.448: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.448: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.448: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.448: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.448: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.448: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.449: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.450: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.450: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.450: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.450: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.450: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.450: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.450: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.450: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.450: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.450: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.450: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.450: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.451: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.451: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.451: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.451: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.451: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.451: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.451: Partial capture successful. Please touch the sensor again (1/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.451: Device reported enroll progress, reported 1 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.452: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.452: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.452: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.452: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.452: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.453: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.453: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.453: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.453: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.453: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.453: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.453: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.453: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.454: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.454: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.454: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.454: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.454: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.454: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.455: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.455: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.455: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.455: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.455: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.455: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.456: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.456: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.456: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.456: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.456: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.456: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.456: Partial capture successful. Please touch the sensor again (2/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.456: Device reported enroll progress, reported 2 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.456: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.456: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.456: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.456: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.457: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.458: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.458: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.458: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.458: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.458: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.458: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.458: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.458: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.459: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.459: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.459: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.459: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.459: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.459: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.460: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.460: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.460: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.460: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.460: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.460: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.460: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.461: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.461: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.461: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.461: Response prefix valid: NO 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.461: Response prefix valid: NO 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.461: Response prefix valid: yes 332s (process:2714): libfprint-device-DEBUG: 05:02:31.461: Device reported enroll progress, reported 2 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.461: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.461: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.461: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.461: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.462: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.462: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.462: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.462: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.462: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.462: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.462: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.462: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.463: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.464: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.464: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.464: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.464: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.464: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.464: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.464: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.464: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.464: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.464: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.464: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.464: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.465: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.465: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.465: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.465: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.465: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.465: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.465: Partial capture successful. Please touch the sensor again (3/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.465: Device reported enroll progress, reported 3 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.465: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.465: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.465: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.465: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.466: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.466: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.467: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.467: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.467: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.467: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.467: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.467: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.467: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.468: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.468: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.468: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.468: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.468: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.468: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.468: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.468: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.468: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.468: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.468: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.468: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.469: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.469: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.469: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.469: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.469: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.469: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.469: Partial capture successful. Please touch the sensor again (4/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.469: Device reported enroll progress, reported 4 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.470: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.470: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.470: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.470: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.470: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.471: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.471: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.471: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.471: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.471: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.471: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.471: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.471: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.472: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.472: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.472: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.472: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.472: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.472: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.472: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.473: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.473: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.473: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.473: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.473: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.473: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.474: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.474: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.474: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.474: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.474: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.474: Partial capture successful. Please touch the sensor again (5/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.474: Device reported enroll progress, reported 5 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.474: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.474: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.474: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.474: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.474: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.475: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.475: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.475: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.475: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.475: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.475: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.475: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.476: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.476: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.476: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.476: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.476: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.476: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.476: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.477: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.477: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.477: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.477: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.477: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.477: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.477: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.478: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.478: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.478: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.478: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.478: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.478: Partial capture successful. Please touch the sensor again (6/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.478: Device reported enroll progress, reported 6 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.478: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.478: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.478: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.478: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.479: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.479: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.479: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.479: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.479: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.479: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.479: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.479: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.480: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.481: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.481: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.481: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.481: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.481: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.481: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.481: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.481: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.481: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.481: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.481: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.481: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.482: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.482: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.482: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.482: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.482: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.482: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.482: Partial capture successful. Please touch the sensor again (7/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.482: Device reported enroll progress, reported 7 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.482: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.482: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.482: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.482: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.483: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.484: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.484: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.484: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.484: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.484: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.484: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.484: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.484: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.485: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.485: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.485: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.485: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.485: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.485: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.485: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.485: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.485: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.485: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.485: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.485: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.486: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.486: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.486: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.486: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.486: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.486: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.486: Partial capture successful. Please touch the sensor again (8/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.486: Device reported enroll progress, reported 8 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.487: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.487: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.487: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.487: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.487: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.488: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.488: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.488: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.488: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.488: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.488: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.488: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.488: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.489: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.489: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.489: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.489: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.489: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.489: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.490: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.490: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.490: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.490: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.490: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.490: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.490: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.491: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.491: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.491: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.491: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.491: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.491: Partial capture successful. Please touch the sensor again (9/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.491: Device reported enroll progress, reported 9 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.491: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.491: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.491: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.491: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.491: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.492: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.492: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.492: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.492: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.492: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.492: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.492: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.493: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.493: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.493: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.493: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.493: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.493: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.493: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.494: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.494: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.494: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.494: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.494: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.494: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.495: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.495: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.495: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.495: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.495: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.495: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.495: Partial capture successful. Please touch the sensor again (10/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.495: Device reported enroll progress, reported 10 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.495: [egismoc] ENROLL_STATES entering state 12 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.495: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.495: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.495: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.496: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.496: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.496: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.496: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.496: [egismoc] ENROLL_STATES entering state 13 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.496: New fingerprint ID: FP1-00000000-2-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.497: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.497: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.497: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.497: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.498: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.498: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.498: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.498: [egismoc] ENROLL_STATES entering state 14 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.498: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.498: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.498: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.498: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.499: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.499: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.499: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.499: [egismoc] ENROLL_STATES entering state 15 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.499: Enrollment was successful! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.499: Device reported enroll completion 332s (process:2714): libfprint-device-DEBUG: 05:02:31.499: Device reported finger status change: FP_FINGER_STATUS_NONE 332s (process:2714): libfprint-device-DEBUG: 05:02:31.499: Print for finger FP_FINGER_LEFT_INDEX enrolled 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.499: [egismoc] ENROLL_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.499: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.499: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.499: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.500: List 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.500: [egismoc] LIST_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.500: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.500: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.500: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.500: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.501: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.501: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.501: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.501: Device fingerprint 1: FP1-00000000-2-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.501: Number of currently enrolled fingerprints on the device is 1 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.501: [egismoc] LIST_STATES entering state 1 332s (process:2714): libfprint-device-DEBUG: 05:02:31.501: Device reported listing completion 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.501: [egismoc] LIST_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.501: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.501: Completing action FPI_DEVICE_ACTION_LIST in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.501: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-device-DEBUG: 05:02:31.501: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.501: Identify or Verify 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.501: [egismoc] IDENTIFY_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.501: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.501: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.501: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.502: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.502: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.503: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.503: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.503: Device fingerprint 1: FP1-00000000-2-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.503: Number of currently enrolled fingerprints on the device is 1 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.503: [egismoc] IDENTIFY_STATES entering state 1 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.503: [egismoc] IDENTIFY_STATES entering state 2 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.503: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.503: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.503: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.503: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.504: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.504: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.504: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.504: [egismoc] IDENTIFY_STATES entering state 3 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.504: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.504: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.504: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.504: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.505: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.505: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.505: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.505: [egismoc] IDENTIFY_STATES entering state 4 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.505: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.505: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.505: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.505: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.505: [egismoc] IDENTIFY_STATES entering state 5 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.505: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.505: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.505: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.506: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.507: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.507: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.507: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.507: [egismoc] IDENTIFY_STATES entering state 6 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.507: Get check command 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.507: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.507: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.507: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.507: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.508: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.508: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.508: Identify check callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.508: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.508: Identify successful for: FP1-00000000-2-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.508: Verifying against: FP1-00000000-2-00000000-nobody 332s (process:2714): libfprint-device-DEBUG: 05:02:31.508: Device reported verify result 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.508: [egismoc] IDENTIFY_STATES entering state 7 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.508: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.508: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.508: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.509: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.509: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.509: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.509: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.509: [egismoc] IDENTIFY_STATES entering state 8 332s (process:2714): libfprint-device-DEBUG: 05:02:31.509: Device reported verify completion 332s (process:2714): libfprint-device-DEBUG: 05:02:31.509: Device reported finger status change: FP_FINGER_STATUS_NONE 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.509: [egismoc] IDENTIFY_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.509: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.509: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.509: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-device-DEBUG: 05:02:31.510: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.510: Identify or Verify 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.510: [egismoc] IDENTIFY_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.510: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.510: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.510: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.511: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.511: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.511: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.511: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.511: Device fingerprint 1: FP1-00000000-2-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.511: Number of currently enrolled fingerprints on the device is 1 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.511: [egismoc] IDENTIFY_STATES entering state 1 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.511: [egismoc] IDENTIFY_STATES entering state 2 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.511: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.511: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.511: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.512: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.513: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.513: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.513: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.513: [egismoc] IDENTIFY_STATES entering state 3 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.513: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.513: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.513: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.513: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.514: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.514: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.514: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.514: [egismoc] IDENTIFY_STATES entering state 4 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.514: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.514: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.514: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.514: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.514: [egismoc] IDENTIFY_STATES entering state 5 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.514: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.514: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.514: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.515: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.516: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.516: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.516: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.516: [egismoc] IDENTIFY_STATES entering state 6 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.516: Get check command 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.516: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.516: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.516: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.516: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.517: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.517: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.517: Identify check callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.517: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.517: Identify successful for: FP1-00000000-2-00000000-nobody 332s (process:2714): libfprint-device-DEBUG: 05:02:31.517: Device reported identify result 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.517: [egismoc] IDENTIFY_STATES entering state 7 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.517: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.517: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.517: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.518: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.518: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.518: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.518: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.518: [egismoc] IDENTIFY_STATES entering state 8 332s (process:2714): libfprint-device-DEBUG: 05:02:31.518: Device reported identify completion 332s (process:2714): libfprint-device-DEBUG: 05:02:31.518: Device reported finger status change: FP_FINGER_STATUS_NONE 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.518: [egismoc] IDENTIFY_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.518: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.519: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.519: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-device-DEBUG: 05:02:31.520: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.520: Enroll 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.520: [egismoc] ENROLL_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.520: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.520: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.520: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.520: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.521: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.521: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.521: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.521: Device fingerprint 1: FP1-00000000-2-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.521: Number of currently enrolled fingerprints on the device is 1 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.521: [egismoc] ENROLL_STATES entering state 1 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.521: [egismoc] ENROLL_STATES entering state 2 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.521: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.521: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.521: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.521: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.522: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.522: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.522: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.522: [egismoc] ENROLL_STATES entering state 3 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.522: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.522: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.522: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.523: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.523: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.523: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.523: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.523: [egismoc] ENROLL_STATES entering state 4 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.523: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.523: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.524: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.524: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.524: [egismoc] ENROLL_STATES entering state 5 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.524: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.524: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.524: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.525: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.525: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.525: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.525: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.525: [egismoc] ENROLL_STATES entering state 6 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.525: Get check command 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.525: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.525: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.525: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.526: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.527: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.527: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.527: Enroll check callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.527: Response suffix valid: NO 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.527: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.527: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.527: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.527: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL 332s (process:2714): libfprint-device-DEBUG: 05:02:31.527: Device reported enroll completion 332s (process:2714): libfprint-device-DEBUG: 05:02:31.527: Device reported finger status change: FP_FINGER_STATUS_NONE 332s (process:2714): libfprint-device-DEBUG: 05:02:31.527: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.527: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.527: List 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.527: [egismoc] LIST_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.527: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.527: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.527: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.528: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.528: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.528: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.528: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.528: Device fingerprint 1: FP1-00000000-2-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.528: Number of currently enrolled fingerprints on the device is 1 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.528: [egismoc] LIST_STATES entering state 1 332s (process:2714): libfprint-device-DEBUG: 05:02:31.528: Device reported listing completion 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.528: [egismoc] LIST_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.528: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.528: Completing action FPI_DEVICE_ACTION_LIST in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.528: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-device-DEBUG: 05:02:31.529: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.529: Enroll 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.529: [egismoc] ENROLL_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.529: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.529: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.529: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.529: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.530: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.530: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.530: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.530: Device fingerprint 1: FP1-00000000-2-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.530: Number of currently enrolled fingerprints on the device is 1 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.530: [egismoc] ENROLL_STATES entering state 1 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.530: [egismoc] ENROLL_STATES entering state 2 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.530: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.530: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.530: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.530: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.531: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.531: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.531: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.531: [egismoc] ENROLL_STATES entering state 3 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.531: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.531: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.531: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.532: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.532: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.532: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.532: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.532: [egismoc] ENROLL_STATES entering state 4 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.532: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.532: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.533: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.533: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.533: [egismoc] ENROLL_STATES entering state 5 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.533: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.533: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.533: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.534: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.534: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.534: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.534: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.534: [egismoc] ENROLL_STATES entering state 6 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.534: Get check command 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.534: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.534: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.534: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.535: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.535: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.535: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.535: Enroll check callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.535: Response suffix valid: yes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.535: [egismoc] ENROLL_STATES entering state 7 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.535: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.535: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.535: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.536: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.537: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.537: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.537: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.537: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.537: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.537: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.537: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.537: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.538: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.538: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.538: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.538: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.538: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.538: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.538: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.538: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.538: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.538: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.538: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.538: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.538: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.538: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.539: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.539: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.539: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.539: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.539: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.539: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.539: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.540: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.540: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.540: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.540: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.540: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.540: Partial capture successful. Please touch the sensor again (1/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.540: Device reported enroll progress, reported 1 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.540: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.540: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.540: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.540: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.541: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.541: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.541: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.541: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.541: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.541: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.541: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.541: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.542: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.542: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.542: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.542: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.542: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.542: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.542: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.543: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.543: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.543: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.543: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.543: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.543: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.543: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.544: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.544: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.544: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.544: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.544: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.544: Partial capture successful. Please touch the sensor again (2/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.544: Device reported enroll progress, reported 2 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.544: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.544: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.544: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.544: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.545: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.546: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.546: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.546: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.546: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.546: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.546: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.546: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.546: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.547: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.547: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.547: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.547: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.547: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.547: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.548: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.548: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.548: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.548: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.548: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.548: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.548: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.549: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.549: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.549: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.549: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.549: Response suffix valid: NO 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.549: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.549: Response suffix valid: yes 332s (process:2714): libfprint-device-DEBUG: 05:02:31.549: Device reported enroll progress, reported 2 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.549: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.549: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.549: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.549: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.550: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.550: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.550: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.551: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.551: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.551: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.551: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.551: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.551: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.552: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.552: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.552: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.552: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.552: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.552: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.553: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.553: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.553: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.553: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.553: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.553: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.553: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.554: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.554: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.554: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.554: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.554: Response suffix valid: NO 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.554: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.554: Response suffix valid: yes 332s (process:2714): libfprint-device-DEBUG: 05:02:31.554: Device reported enroll progress, reported 2 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.554: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.554: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.554: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.554: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.555: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.555: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.555: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.555: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.555: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.556: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.556: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.556: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.556: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.557: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.557: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.557: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.557: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.557: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.557: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.557: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.557: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.558: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.558: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.558: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.558: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.558: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.559: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.559: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.559: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.559: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.559: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.559: Partial capture successful. Please touch the sensor again (3/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.559: Device reported enroll progress, reported 3 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.559: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.559: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.559: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.559: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.559: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.560: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.560: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.560: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.560: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.560: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.560: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.560: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.561: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.561: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.561: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.561: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.561: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.561: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.561: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.562: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.562: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.562: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.562: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.562: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.562: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.563: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.563: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.563: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.563: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.563: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.563: Response suffix valid: NO 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.563: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.563: Response suffix valid: yes 332s (process:2714): libfprint-device-DEBUG: 05:02:31.563: Device reported enroll progress, reported 3 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.563: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.563: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.563: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.563: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.564: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.565: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.565: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.565: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.565: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.565: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.565: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.565: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.565: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.566: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.566: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.566: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.566: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.566: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.566: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.567: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.567: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.567: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.567: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.567: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.567: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.568: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.568: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.568: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.568: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.568: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.568: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.568: Partial capture successful. Please touch the sensor again (4/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.568: Device reported enroll progress, reported 4 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.569: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.569: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.569: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.569: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.569: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.570: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.570: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.570: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.570: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.570: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.570: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.570: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.571: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.571: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.571: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.571: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.571: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.571: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.571: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.572: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.572: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.572: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.572: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.572: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.572: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.573: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.573: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.573: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.573: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.573: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.573: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.573: Partial capture successful. Please touch the sensor again (5/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.573: Device reported enroll progress, reported 5 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.573: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.573: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.573: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.573: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.574: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.575: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.575: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.575: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.575: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.575: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.575: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.575: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.575: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.576: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.576: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.576: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.576: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.576: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.576: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.577: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.577: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.577: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.577: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.577: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.577: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.577: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.578: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.578: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.578: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.578: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.578: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.578: Partial capture successful. Please touch the sensor again (6/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.578: Device reported enroll progress, reported 6 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.578: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.578: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.578: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.578: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.579: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.579: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.579: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.580: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.580: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.580: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.580: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.580: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.580: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.581: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.581: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.581: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.581: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.581: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.581: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.581: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.581: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.581: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.581: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.581: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.581: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.582: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.583: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.583: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.583: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.583: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.583: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.583: Partial capture successful. Please touch the sensor again (7/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.583: Device reported enroll progress, reported 7 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.583: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.583: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.583: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.583: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.583: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.584: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.584: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.584: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.584: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.584: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.584: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.584: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.585: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.586: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.586: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.586: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.586: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.586: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.586: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.586: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.586: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.586: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.586: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.586: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.586: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.587: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.587: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.587: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.587: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.587: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.587: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.587: Partial capture successful. Please touch the sensor again (8/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.587: Device reported enroll progress, reported 8 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.588: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.588: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.588: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.588: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.588: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.589: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.589: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.589: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.589: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.589: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.589: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.589: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.589: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.590: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.590: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.590: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.590: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.590: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.590: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.591: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.591: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.591: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.591: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.591: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.591: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.591: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.592: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.592: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.592: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.592: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.592: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.592: Partial capture successful. Please touch the sensor again (9/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.592: Device reported enroll progress, reported 9 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.592: [egismoc] ENROLL_STATES entering state 8 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.592: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.592: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.592: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.592: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.593: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.593: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.593: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.593: [egismoc] ENROLL_STATES entering state 9 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.593: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.593: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.593: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.594: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.595: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.595: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.595: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.595: [egismoc] ENROLL_STATES entering state 10 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.595: Wait for finger on sensor 332s (process:2714): libfprint-device-DEBUG: 05:02:31.595: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.595: Finger on sensor callback 332s (process:2714): libfprint-device-DEBUG: 05:02:31.595: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.595: [egismoc] ENROLL_STATES entering state 11 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.595: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.595: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.595: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.596: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.596: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.596: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.596: Read capture callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.596: Response prefix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.596: Response suffix valid: yes 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.596: Partial capture successful. Please touch the sensor again (10/10) 332s (process:2714): libfprint-device-DEBUG: 05:02:31.596: Device reported enroll progress, reported 10 of 10 have been completed 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.596: [egismoc] ENROLL_STATES entering state 12 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.596: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.596: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.596: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.599: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.600: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.600: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.600: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.600: [egismoc] ENROLL_STATES entering state 13 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.600: New fingerprint ID: FP1-00000000-7-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.600: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.600: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.600: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.601: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.601: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.601: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.601: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.601: [egismoc] ENROLL_STATES entering state 14 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.601: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.601: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.601: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.602: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.602: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.602: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.602: Task SSM next state callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.602: [egismoc] ENROLL_STATES entering state 15 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.602: Enrollment was successful! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.602: Device reported enroll completion 332s (process:2714): libfprint-device-DEBUG: 05:02:31.602: Device reported finger status change: FP_FINGER_STATUS_NONE 332s (process:2714): libfprint-device-DEBUG: 05:02:31.602: Print for finger FP_FINGER_RIGHT_INDEX enrolled 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.602: [egismoc] ENROLL_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.602: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.602: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.602: Updated temperature model after 0.07 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.603: List 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.603: [egismoc] LIST_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.603: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.603: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.603: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.603: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.604: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.604: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.604: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.604: Device fingerprint 1: FP1-00000000-2-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.604: Device fingerprint 2: FP1-00000000-7-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.604: Number of currently enrolled fingerprints on the device is 2 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.604: [egismoc] LIST_STATES entering state 1 332s (process:2714): libfprint-device-DEBUG: 05:02:31.604: Device reported listing completion 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.604: [egismoc] LIST_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.604: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.604: Completing action FPI_DEVICE_ACTION_LIST in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.604: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.605: Delete 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.605: [egismoc] DELETE_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.605: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.605: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.605: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.605: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.606: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.606: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.606: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.606: Device fingerprint 1: FP1-00000000-2-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.606: Device fingerprint 2: FP1-00000000-7-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.606: Number of currently enrolled fingerprints on the device is 2 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.606: [egismoc] DELETE_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.606: Get delete command 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.606: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody) 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.606: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.606: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.606: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.607: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.607: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.607: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.608: Delete callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.608: Response prefix valid: yes 332s (process:2714): libfprint-device-DEBUG: 05:02:31.608: Device reported deletion completion 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.608: [egismoc] DELETE_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.608: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.608: Completing action FPI_DEVICE_ACTION_DELETE in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.608: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.608: List 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.608: [egismoc] LIST_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.608: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.608: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.608: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.608: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.609: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.609: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.609: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.609: Device fingerprint 1: FP1-00000000-7-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.609: Number of currently enrolled fingerprints on the device is 1 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.609: [egismoc] LIST_STATES entering state 1 332s (process:2714): libfprint-device-DEBUG: 05:02:31.609: Device reported listing completion 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.609: [egismoc] LIST_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.609: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.609: Completing action FPI_DEVICE_ACTION_LIST in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.609: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.609: Clear storage 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.609: [egismoc] DELETE_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.609: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.609: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.610: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.610: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.611: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.611: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.611: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.611: Device fingerprint 1: FP1-00000000-7-00000000-nobody 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.611: Number of currently enrolled fingerprints on the device is 1 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.611: [egismoc] DELETE_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.611: Get delete command 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.611: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.611: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.611: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.612: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.612: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.612: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.612: Delete callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.612: Response prefix valid: yes 332s (process:2714): libfprint-device-DEBUG: 05:02:31.612: Device reported deletion completion 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.612: [egismoc] DELETE_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.612: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.612: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.612: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.612: List 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.612: [egismoc] LIST_STATES entering state 0 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.612: Execute command and get response 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.612: Get check bytes 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.612: [egismoc] CMD_STATES entering state 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.613: [egismoc] CMD_STATES entering state 1 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.614: Command receive callback 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.614: [egismoc] CMD_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.614: List callback 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.614: Number of currently enrolled fingerprints on the device is 0 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.614: [egismoc] LIST_STATES entering state 1 332s (process:2714): libfprint-device-DEBUG: 05:02:31.614: Device reported listing completion 332s (process:2714): libfprint-SSM-DEBUG: 05:02:31.614: [egismoc] LIST_STATES completed successfully 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.614: Task SSM done 332s (process:2714): libfprint-device-DEBUG: 05:02:31.614: Completing action FPI_DEVICE_ACTION_LIST in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.614: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.614: Closing device 332s (process:2714): libfprint-egismoc-DEBUG: 05:02:31.614: Cancel 332s (process:2714): libfprint-device-DEBUG: 05:02:31.614: Device reported close completion 332s (process:2714): libfprint-device-DEBUG: 05:02:31.615: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 332s (process:2714): libfprint-device-DEBUG: 05:02:31.615: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 332s listing - device should have prints 332s clear device storage 332s clear done 332s listing - device should be empty 332s enrolling 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 1, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 2, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 2, None, None, GLib.Error('Your device is having trouble recognizing you. Make sure your sensor is clean.', 'fp - device - retry - quark', 3)) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 3, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 4, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 5, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 6, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 7, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 8, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 9, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 10, , None, None) 332s enroll done 332s listing - device should have 1 print 332s verifying 332s verify done 332s async identifying 332s indentification_done: 332s try to enroll duplicate 332s duplicate enroll attempt done 332s listing - device should still only have 1 print 332s enroll new finger 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 1, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 2, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 3, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 4, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 5, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 6, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 7, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 8, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 9, , None, None) 332s finger status: 332s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0xea80fcf22500 (FpiDeviceEgisMoc at 0xbfdf4f0)>, 10, , None, None) 332s enroll new finger done 332s listing - device should have 2 prints 332s deleting first print 332s delete done 332s listing - device should only have second print 332s clear device storage 332s clear done 332s listing - device should be empty 332s ** (umockdev-run:2710): DEBUG: 05:02:31.649: umockdev.vala:154: Removing test bed /tmp/umockdev.C5AJ22 332s (umockdev-run:2710): GLib-DEBUG: 05:02:31.654: unsetenv() is not thread-safe and should not be used after threads are created 332s PASS: libfprint-2/driver-egismoc-05a1.test 332s Running test: libfprint-2/driver-upektc_img-tcs1s.test 332s ** (umockdev-run:2722): DEBUG: 05:02:31.769: umockdev.vala:127: Created udev test bed /tmp/umockdev.KAQ312 332s ** (umockdev-run:2722): DEBUG: 05:02:31.769: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 332s ** (umockdev-run:2722): DEBUG: 05:02:31.774: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 (subsystem usb) 332s ** (umockdev-run:2722): DEBUG: 05:02:31.776: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.KAQ312/dev/bus/usb/003/004 332s ** (umockdev-run:2722): DEBUG: 05:02:31.776: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 332s ** (umockdev-run:2722): DEBUG: 05:02:31.780: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 (subsystem usb) 332s ** (umockdev-run:2722): DEBUG: 05:02:31.782: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.KAQ312/dev/bus/usb/003/001 332s ** (umockdev-run:2722): DEBUG: 05:02:31.782: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4 332s ** (umockdev-run:2722): DEBUG: 05:02:31.784: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4 (subsystem pci) 332s ** (umockdev-run:2722): DEBUG: 05:02:31.786: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1 332s ** (umockdev-run:2722): DEBUG: 05:02:31.787: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1 (subsystem pci) 332s (process:2726): libfprint-context-DEBUG: 05:02:31.895: Initializing FpContext (libfprint version 1.94.9+tod1) 332s (process:2726): libfprint-tod-DEBUG: 05:02:31.895: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 332s (process:2726): libfprint-context-DEBUG: 05:02:31.897: No driver found for USB device 1D6B:0002 332s (process:2726): libfprint-device-DEBUG: 05:02:31.898: Device reported probe completion 332s (process:2726): libfprint-device-DEBUG: 05:02:31.898: Completing action FPI_DEVICE_ACTION_PROBE in idle! 332s (process:2726): libfprint-device-DEBUG: 05:02:31.898: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.900: Image device open completed 332s (process:2726): libfprint-device-DEBUG: 05:02:31.900: Device reported open completion 332s (process:2726): libfprint-device-DEBUG: 05:02:31.900: Completing action FPI_DEVICE_ACTION_OPEN in idle! 332s (process:2726): libfprint-device-DEBUG: 05:02:31.900: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 332s (process:2726): libfprint-device-DEBUG: 05:02:31.900: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.900: Activating image device 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.900: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.900: [upektc_img] ACTIVATE_NUM_STATES entering state 0 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.901: [upektc_img] ACTIVATE_NUM_STATES entering state 1 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.902: [upektc_img] ACTIVATE_NUM_STATES entering state 2 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.903: [upektc_img] ACTIVATE_NUM_STATES entering state 3 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.904: [upektc_img] ACTIVATE_NUM_STATES entering state 4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.904: [upektc_img] ACTIVATE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.905: [upektc_img] ACTIVATE_NUM_STATES entering state 6 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.905: [upektc_img] ACTIVATE_NUM_STATES entering state 7 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.906: [upektc_img] ACTIVATE_NUM_STATES entering state 8 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.906: [upektc_img] ACTIVATE_NUM_STATES entering state 9 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.907: [upektc_img] ACTIVATE_NUM_STATES entering state 10 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.908: [upektc_img] ACTIVATE_NUM_STATES entering state 11 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.908: Sensor type : TCS1x, width x height: 256 x 360 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.908: [upektc_img] ACTIVATE_NUM_STATES completed successfully 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.908: Image device activation completed 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.908: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.908: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON 332s (process:2726): libfprint-device-DEBUG: 05:02:31.908: Device reported finger status change: FP_FINGER_STATUS_NEEDED 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.908: [upektc_img] CAPTURE_NUM_STATES entering state 0 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.909: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.910: request completed, len: 0000 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.910: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.911: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.911: 18th byte is 0c 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.911: [upektc_img] CAPTURE_NUM_STATES entering state 3 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.911: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.912: request completed, len: 0000 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.912: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.912: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.912: 18th byte is 13 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.912: [upektc_img] CAPTURE_NUM_STATES entering state 3 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.913: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.913: request completed, len: 0000 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.913: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.914: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.914: 18th byte is 00 332s (process:2726): libfprint-device-DEBUG: 05:02:31.914: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.914: [upektc_img] CAPTURE_NUM_STATES entering state 3 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.915: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.915: request completed, len: 0000 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.915: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.915: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.916: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.916: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.916: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.916: request completed, len: 07c4 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.916: Image device reported finger status: on 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.916: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.916: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.917: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.917: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.917: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.917: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.917: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.918: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.918: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.918: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.919: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.919: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.919: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.919: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.919: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.919: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.920: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.921: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.921: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.921: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.921: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.922: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.922: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.922: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.923: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.923: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.923: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.923: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.923: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.923: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.924: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.925: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.925: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.925: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.925: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.925: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.925: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.926: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.926: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.926: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.926: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.926: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.927: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.927: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.927: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.928: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.928: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.928: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.928: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.929: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.929: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.929: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.930: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.930: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.930: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.930: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.931: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.931: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.931: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.932: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.932: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.932: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.932: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.933: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.933: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.933: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.934: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.934: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.934: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.934: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.934: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.934: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.935: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.935: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.935: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.935: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.935: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.936: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.936: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.937: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.937: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.937: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.937: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.937: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.938: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.938: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.938: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.939: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.939: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.939: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.939: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.940: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.940: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.940: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.941: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.941: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.941: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.941: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.941: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.941: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.942: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.942: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.943: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.943: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.943: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.943: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.943: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.944: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.944: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.944: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.944: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.944: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.945: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.945: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.945: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.946: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.946: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.946: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.946: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.946: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.946: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.947: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.947: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.948: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.948: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.948: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.948: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.948: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.949: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.949: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.949: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.949: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.949: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.950: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.950: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.950: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.951: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.951: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.951: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.951: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.951: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.951: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.952: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.953: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.953: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.953: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.953: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.953: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.953: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.954: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.954: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.954: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.954: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.954: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.955: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.955: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.955: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.956: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.956: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.956: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.956: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.956: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.957: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.957: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.957: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.957: response_size is 2052, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.957: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.957: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.958: request completed, len: 07c4 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.958: [upektc_img] CAPTURE_NUM_STATES entering state 5 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.959: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.959: request completed, len: 0040 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.959: response_size is 814, actual_length is 64 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.959: Waiting for rest of transfer 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.959: [upektc_img] CAPTURE_NUM_STATES entering state 1 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.960: request completed, len: 02ee 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.960: Image size is 51840 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.960: Image device captured an image 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.960: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF 332s (process:2726): libfprint-device-DEBUG: 05:02:31.960: Device reported finger status change: FP_FINGER_STATUS_PRESENT 332s (process:2726): libfprint-device-DEBUG: 05:02:31.960: Device reported finger status change: FP_FINGER_STATUS_NONE 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.960: Image device reported finger status: off 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.960: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.960: Deactivating image device 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.960: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.960: [upektc_img] CAPTURE_NUM_STATES completed successfully 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.960: [upektc_img] DEACTIVATE_NUM_STATES entering state 0 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.962: [upektc_img] DEACTIVATE_NUM_STATES entering state 1 332s (process:2726): libfprint-SSM-DEBUG: 05:02:31.963: [upektc_img] DEACTIVATE_NUM_STATES completed successfully 332s (process:2726): libfprint-upektc_img-DEBUG: 05:02:31.963: Deactivate completed 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.963: Image device deactivation completed 332s (process:2726): libfprint-image_device-DEBUG: 05:02:31.963: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE 333s (process:2726): libfprint-image-DEBUG: 05:02:31.986: Minutiae scan completed in 0.025926 secs 333s (process:2726): libfprint-device-DEBUG: 05:02:31.987: Device reported capture completion 333s (process:2726): libfprint-device-DEBUG: 05:02:31.987: Completing action FPI_DEVICE_ACTION_CAPTURE in idle! 333s (process:2726): libfprint-device-DEBUG: 05:02:31.987: Updated temperature model after 0.09 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM 333s (process:2726): libfprint-image_device-DEBUG: 05:02:31.987: Image device close completed 333s (process:2726): libfprint-device-DEBUG: 05:02:31.988: Device reported close completion 333s (process:2726): libfprint-device-DEBUG: 05:02:31.988: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 333s (process:2726): libfprint-device-DEBUG: 05:02:31.988: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM 333s ** (umockdev-run:2722): DEBUG: 05:02:32.096: umockdev.vala:154: Removing test bed /tmp/umockdev.KAQ312 333s (umockdev-run:2722): GLib-DEBUG: 05:02:32.103: unsetenv() is not thread-safe and should not be used after threads are created 333s Comparing PNGs /tmp/libfprint-umockdev-test-v2f9ubrp/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img-tcs1s/capture.png 333s PASS: libfprint-2/driver-upektc_img-tcs1s.test 333s Running test: libfprint-2/driver-focaltech_moc.test 333s ** (umockdev-run:2735): DEBUG: 05:02:32.185: umockdev.vala:127: Created udev test bed /tmp/umockdev.3CWF22 333s ** (umockdev-run:2735): DEBUG: 05:02:32.185: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 333s ** (umockdev-run:2735): DEBUG: 05:02:32.189: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 (subsystem usb) 333s ** (umockdev-run:2735): DEBUG: 05:02:32.192: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3CWF22/dev/bus/usb/003/006 333s ** (umockdev-run:2735): DEBUG: 05:02:32.192: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 333s ** (umockdev-run:2735): DEBUG: 05:02:32.196: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 (subsystem usb) 333s ** (umockdev-run:2735): DEBUG: 05:02:32.198: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3CWF22/dev/bus/usb/003/002 333s ** (umockdev-run:2735): DEBUG: 05:02:32.198: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 333s ** (umockdev-run:2735): DEBUG: 05:02:32.201: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 (subsystem usb) 333s ** (umockdev-run:2735): DEBUG: 05:02:32.203: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3CWF22/dev/bus/usb/003/001 333s ** (umockdev-run:2735): DEBUG: 05:02:32.203: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 333s ** (umockdev-run:2735): DEBUG: 05:02:32.205: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 (subsystem pci) 333s ** (umockdev-run:2735): DEBUG: 05:02:32.207: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4 333s ** (umockdev-run:2735): DEBUG: 05:02:32.208: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4 (subsystem pci) 333s (process:2739): libfprint-context-DEBUG: 05:02:32.314: Initializing FpContext (libfprint version 1.94.9+tod1) 333s (process:2739): libfprint-tod-DEBUG: 05:02:32.314: Impossible to load the shared drivers dir Error opening directory “/usr/lib/aarch64-linux-gnu/libfprint-2/tod-1”: No such file or directory 333s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:32.317: 110235318: ../libfprint/drivers/focaltech_moc/focaltech_moc.c:1852 333s (process:2739): libfprint-context-DEBUG: 05:02:32.317: No driver found for USB device 05E3:0608 333s (process:2739): libfprint-context-DEBUG: 05:02:32.317: No driver found for USB device 1D6B:0002 333s (process:2739): libfprint-device-DEBUG: 05:02:32.317: Device reported probe completion 333s (process:2739): libfprint-device-DEBUG: 05:02:32.317: Completing action FPI_DEVICE_ACTION_PROBE in idle! 333s (process:2739): libfprint-device-DEBUG: 05:02:32.317: Not updating temperature model, device can run continuously! 333s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 333s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline? 333s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:32.319: class:dc, subclass:a0, protocol:b0 333s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:32.319: bytes size:0 333s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:32.319: 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 333s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:32.319: bytes size:0 333s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:32.319: 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 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.320: [focaltech_moc] DEV_INIT_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.320: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.320: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:32.321: focaltechmoc enroll_times: 10 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.321: [focaltech_moc] DEV_INIT_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.321: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.321: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.322: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.323: [focaltech_moc] DEV_INIT_STATES completed successfully 333s (process:2739): libfprint-device-DEBUG: 05:02:32.323: Device reported open completion 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.323: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-device-DEBUG: 05:02:32.323: Completing action FPI_DEVICE_ACTION_OPEN in idle! 333s (process:2739): libfprint-device-DEBUG: 05:02:32.323: Not updating temperature model, device can run continuously! 333s (process:2739): libfprint-device-DEBUG: 05:02:32.323: Not updating temperature model, device can run continuously! 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.323: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.323: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.324: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.325: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.325: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.325: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.325: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.326: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 2 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.326: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.327: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.327: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.327: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 3 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.328: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.328: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.328: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:32.329: focaltechmoc user id: FP1-00000000-0-00000000-nobody 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.329: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.329: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.329: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.329: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.330: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.330: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.380: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.380: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.381: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.381: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.381: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.431: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.432: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.432: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.433: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.433: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.483: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.483: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.483: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.484: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.484: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.534: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.534: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.535: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.535: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.535: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.586: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.586: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.586: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.587: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.587: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.637: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.637: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.637: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.638: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.638: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.638: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.639: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-device-DEBUG: 05:02:32.639: Device reported enroll progress, reported 1 of 10 have been completed 333s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:32.639: focaltechmoc remain: 9 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.639: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.639: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.640: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.640: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.641: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.641: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.691: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.691: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.691: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.692: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.692: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.742: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.742: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.743: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.743: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.743: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.793: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.793: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.794: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.795: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.795: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.845: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.845: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.845: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.846: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.846: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.896: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.896: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.897: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.897: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.897: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.898: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.898: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-device-DEBUG: 05:02:32.899: Device reported enroll progress, reported 2 of 10 have been completed 333s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:32.899: focaltechmoc remain: 8 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.899: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.899: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.899: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.899: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.900: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.900: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.950: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.950: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.951: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.951: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.951: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.952: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.952: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-device-DEBUG: 05:02:32.952: Device reported enroll progress, reported 3 of 10 have been completed 333s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:32.952: focaltechmoc remain: 7 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.952: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.953: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.953: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.953: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.954: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 333s (process:2739): libfprint-SSM-DEBUG: 05:02:32.954: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.004: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.004: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.004: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.005: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.005: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.055: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.055: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.056: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.056: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.056: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.106: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.106: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.107: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.108: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.108: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.158: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.158: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.158: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.159: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.159: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.209: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.209: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.210: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.210: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.210: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.211: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.211: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-device-DEBUG: 05:02:33.211: Device reported enroll progress, reported 4 of 10 have been completed 334s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:33.212: focaltechmoc remain: 6 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.212: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.212: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.212: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.212: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.213: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.213: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.263: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.263: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.263: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.264: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.264: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.314: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.314: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.315: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.315: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.315: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.365: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.365: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.366: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.367: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.367: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.367: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.367: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-device-DEBUG: 05:02:33.368: Device reported enroll progress, reported 5 of 10 have been completed 334s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:33.368: focaltechmoc remain: 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.368: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.368: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.368: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.368: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.369: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.369: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.419: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.419: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.420: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.420: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.420: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.471: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.471: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.471: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.472: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.472: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.522: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.522: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.522: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.523: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.523: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.573: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.573: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.574: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.574: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.574: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.575: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.575: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-device-DEBUG: 05:02:33.575: Device reported enroll progress, reported 6 of 10 have been completed 334s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:33.575: focaltechmoc remain: 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.575: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.575: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.576: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.576: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.577: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.577: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.577: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.577: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-device-DEBUG: 05:02:33.578: Device reported enroll progress, reported 6 of 10 have been completed 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.578: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.578: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.578: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.579: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.579: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.579: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.629: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.629: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.630: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.630: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.630: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.681: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.681: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.681: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.682: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.682: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.732: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.732: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.732: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.733: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.733: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.783: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.783: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.784: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.784: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.784: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.785: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.785: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-device-DEBUG: 05:02:33.786: Device reported enroll progress, reported 7 of 10 have been completed 334s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:33.786: focaltechmoc remain: 3 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.786: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.786: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.786: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.786: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.787: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.787: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.837: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.837: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.838: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.838: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.838: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.888: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.888: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.889: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.889: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.890: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.890: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.890: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-device-DEBUG: 05:02:33.891: Device reported enroll progress, reported 8 of 10 have been completed 334s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:33.891: focaltechmoc remain: 2 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.891: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.891: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.891: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.891: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.892: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.892: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.942: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.942: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.943: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.943: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.943: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.944: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.944: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-device-DEBUG: 05:02:33.944: Device reported enroll progress, reported 9 of 10 have been completed 334s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:33.944: focaltechmoc remain: 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.944: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.944: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.945: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.945: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.946: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5 334s (process:2739): libfprint-SSM-DEBUG: 05:02:33.946: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:33.996: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4 335s (process:2739): libfprint-SSM-DEBUG: 05:02:33.996: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:33.996: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:33.997: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6 335s (process:2739): libfprint-SSM-DEBUG: 05:02:33.997: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:33.997: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:33.998: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-device-DEBUG: 05:02:33.998: Device reported enroll progress, reported 10 of 10 have been completed 335s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:33.998: focaltechmoc remain: 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:33.998: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 7 335s (process:2739): libfprint-SSM-DEBUG: 05:02:33.998: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:33.999: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:33.999: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:33.999: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 8 335s (process:2739): libfprint-SSM-DEBUG: 05:02:33.999: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.000: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.000: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:34.001: focaltech_moc_commit_cb success 335s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:34.001: Enrollment was successful! 335s (process:2739): libfprint-device-DEBUG: 05:02:34.001: Device reported enroll completion 335s (process:2739): libfprint-device-DEBUG: 05:02:34.001: Print for finger FP_FINGER_UNKNOWN enrolled 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.001: [focaltech_moc] MOC_ENROLL_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.001: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-device-DEBUG: 05:02:34.001: Completing action FPI_DEVICE_ACTION_ENROLL in idle! 335s (process:2739): libfprint-device-DEBUG: 05:02:34.001: Not updating temperature model, device can run continuously! 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.001: [focaltech_moc] MOC_LIST_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.001: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.001: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.002: [focaltech_moc] MOC_LIST_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.002: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.002: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.002: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:34.003: focaltechmoc add slot: 0 335s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:34.003: FP1-00000000-0-00000000-nobody 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.003: [focaltech_moc] MOC_LIST_NUM_STATES entering state 2 335s (process:2739): libfprint-device-DEBUG: 05:02:34.003: Device reported listing completion 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.003: [focaltech_moc] MOC_LIST_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.003: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-device-DEBUG: 05:02:34.003: Completing action FPI_DEVICE_ACTION_LIST in idle! 335s (process:2739): libfprint-device-DEBUG: 05:02:34.003: Not updating temperature model, device can run continuously! 335s (process:2739): libfprint-device-DEBUG: 05:02:34.004: Not updating temperature model, device can run continuously! 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.004: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.004: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.004: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.005: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.005: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.005: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.005: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.006: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.006: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.056: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.056: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.057: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.057: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.057: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s Executing: libfprint-2/driver-focaltech_moc.test 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.107: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.107: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.108: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.108: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.108: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.159: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.159: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.159: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.160: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.160: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.210: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.210: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.210: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.211: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.211: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.211: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.212: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.212: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.212: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.213: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.213: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-device-DEBUG: 05:02:34.213: Device reported verify result 335s (process:2739): libfprint-device-DEBUG: 05:02:34.213: Device reported verify completion 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.213: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.213: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-device-DEBUG: 05:02:34.214: Completing action FPI_DEVICE_ACTION_VERIFY in idle! 335s (process:2739): libfprint-device-DEBUG: 05:02:34.214: Not updating temperature model, device can run continuously! 335s (process:2739): libfprint-device-DEBUG: 05:02:34.214: Not updating temperature model, device can run continuously! 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.214: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.214: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.215: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.215: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.215: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.216: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.216: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.216: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.216: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.266: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.266: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.267: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.268: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.268: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.318: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.318: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.318: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.319: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.319: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.319: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.319: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.320: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.320: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.320: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.320: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-device-DEBUG: 05:02:34.321: Device reported identify result 335s (process:2739): libfprint-device-DEBUG: 05:02:34.321: Device reported identify completion 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.321: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.321: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-device-DEBUG: 05:02:34.321: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle! 335s (process:2739): libfprint-device-DEBUG: 05:02:34.321: Not updating temperature model, device can run continuously! 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.322: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.322: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.322: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.323: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.323: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.323: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.323: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:34.324: focaltechmoc add slot: 0 335s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:34.324: FP1-00000000-0-00000000-nobody 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.324: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 2 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.324: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.324: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.325: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.325: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.325: [focaltech_moc] FP_CMD_NUM_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.325: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.326: [focaltech_moc] FP_CMD_NUM_STATES entering state 1 335s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:34.326: delete slot 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.326: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.326: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 4 335s (process:2739): libfprint-device-DEBUG: 05:02:34.326: Device reported deletion completion 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.326: [focaltech_moc] MOC_DELETE_NUM_STATES completed successfully 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.326: [focaltech_moc] FP_CMD_NUM_STATES completed successfully 335s (process:2739): libfprint-device-DEBUG: 05:02:34.326: Completing action FPI_DEVICE_ACTION_DELETE in idle! 335s (process:2739): libfprint-device-DEBUG: 05:02:34.326: Not updating temperature model, device can run continuously! 335s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:34.327: Focaltechmoc dev_exit 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.327: [focaltech_moc] DEV_EXIT_STATES entering state 0 335s (process:2739): libfprint-SSM-DEBUG: 05:02:34.327: [focaltech_moc] DEV_EXIT_STATES completed successfully 335s (process:2739): libfprint-focaltech_moc-DEBUG: 05:02:34.327: class:dc, subclass:a0, protocol:b0 335s (process:2739): libfprint-device-DEBUG: 05:02:34.327: Device reported close completion 335s (process:2739): libfprint-device-DEBUG: 05:02:34.327: Completing action FPI_DEVICE_ACTION_CLOSE in idle! 335s (process:2739): libfprint-device-DEBUG: 05:02:34.327: Not updating temperature model, device can run continuously! 335s enrolling 335s finger status: 335s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf49687fda2c0 (FpiDeviceFocaltechMoc at 0x24a6b980)>, 1, None, None, None) 335s finger status: 335s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf49687fda2c0 (FpiDeviceFocaltechMoc at 0x24a6b980)>, 2, None, None, None) 335s finger status: 335s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf49687fda2c0 (FpiDeviceFocaltechMoc at 0x24a6b980)>, 3, None, None, None) 335s finger status: 335s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf49687fda2c0 (FpiDeviceFocaltechMoc at 0x24a6b980)>, 4, None, None, None) 335s finger status: 335s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf49687fda2c0 (FpiDeviceFocaltechMoc at 0x24a6b980)>, 5, None, None, None) 335s finger status: 335s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf49687fda2c0 (FpiDeviceFocaltechMoc at 0x24a6b980)>, 6, None, None, None) 335s finger status: 335s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf49687fda2c0 (FpiDeviceFocaltechMoc at 0x24a6b980)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2)) 335s finger status: 335s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf49687fda2c0 (FpiDeviceFocaltechMoc at 0x24a6b980)>, 7, None, None, None) 335s finger status: 335s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf49687fda2c0 (FpiDeviceFocaltechMoc at 0x24a6b980)>, 8, None, None, None) 335s finger status: 335s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf49687fda2c0 (FpiDeviceFocaltechMoc at 0x24a6b980)>, 9, None, None, None) 335s finger status: 335s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0xf49687fda2c0 (FpiDeviceFocaltechMoc at 0x24a6b980)>, 10, None, None, None) 335s enroll done 335s listing 335s listing done 335s verifying 335s verify done 335s async identifying 335s indentification_done: 335s deleting 335s delete done 335s ** (umockdev-run:2735): DEBUG: 05:02:34.358: umockdev.vala:154: Removing test bed /tmp/umockdev.3CWF22 335s (umockdev-run:2735): GLib-DEBUG: 05:02:34.364: unsetenv() is not thread-safe and should not be used after threads are created 335s PASS: libfprint-2/driver-focaltech_moc.test 335s SUMMARY: total=36; passed=36; skipped=0; failed=0; user=24.8s; system=10.8s; maxrss=44476 335s autopkgtest [05:02:34]: test installed-tests: -----------------------] 336s installed-tests PASS 336s autopkgtest [05:02:35]: test installed-tests: - - - - - - - - - - results - - - - - - - - - - 336s autopkgtest [05:02:35]: @@@@@@@@@@@@@@@@@@@@ summary 336s installed-tests PASS 341s nova [W] Using flock in prodstack6-arm64 341s Creating nova instance adt-plucky-arm64-libfprint-20250222-045659-juju-7f2275-prod-proposed-migration-environment-15-b2f8f23d-4e12-4008-9c50-5e7384daa1a6 from image adt/ubuntu-plucky-arm64-server-20250221.img (UUID 7cc4cd7e-6f5b-4658-9b17-e38e7fa05fb0)... 341s nova [W] Timed out waiting for 077955f8-bf80-4f87-a6e5-54e687021a4b to get deleted.