0s autopkgtest [05:00:11]: starting date and time: 2025-02-22 05:00:11+0000
  0s autopkgtest [05:00:11]: git checkout: 325255d2 Merge branch 'pin-any-arch' into 'ubuntu/production'
  0s autopkgtest [05:00:11]: host juju-7f2275-prod-proposed-migration-environment-15; command line: /home/ubuntu/autopkgtest/runner/autopkgtest --output-dir /tmp/autopkgtest-work.1r58irqp/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-s390x --security-groups autopkgtest-juju-7f2275-prod-proposed-migration-environment-15@bos03-s390x-11.secgroup --name adt-plucky-s390x-libfprint-20250222-050011-juju-7f2275-prod-proposed-migration-environment-15-7cb8cb3a-b960-4f3e-8c60-0f7bc457f82e --image adt/ubuntu-plucky-s390x-server --keyname testbed-juju-7f2275-prod-proposed-migration-environment-15 --net-id=net_prod-proposed-migration-s390x -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/
108s autopkgtest [05:01:59]: testbed dpkg architecture: s390x
108s autopkgtest [05:01:59]: testbed apt version: 2.9.30ubuntu1
108s autopkgtest [05:01:59]: @@@@@@@@@@@@@@@@@@@@ test bed setup
108s autopkgtest [05:01:59]: testbed release detected to be: None
109s autopkgtest [05:02:00]: updating testbed package index (apt update)
109s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed InRelease [110 kB]
110s Hit:2 http://ftpmaster.internal/ubuntu plucky InRelease
110s Hit:3 http://ftpmaster.internal/ubuntu plucky-updates InRelease
110s Hit:4 http://ftpmaster.internal/ubuntu plucky-security InRelease
110s Get:5 http://ftpmaster.internal/ubuntu plucky-proposed/universe Sources [508 kB]
110s Get:6 http://ftpmaster.internal/ubuntu plucky-proposed/main Sources [80.1 kB]
110s Get:7 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse Sources [13.5 kB]
110s Get:8 http://ftpmaster.internal/ubuntu plucky-proposed/restricted Sources [3120 B]
110s Get:9 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x Packages [123 kB]
110s Get:10 http://ftpmaster.internal/ubuntu plucky-proposed/restricted s390x Packages [760 B]
110s Get:11 http://ftpmaster.internal/ubuntu plucky-proposed/universe s390x Packages [423 kB]
110s Get:12 http://ftpmaster.internal/ubuntu plucky-proposed/multiverse s390x Packages [2816 B]
110s Fetched 1265 kB in 1s (1426 kB/s)
111s Reading package lists...
111s + lsb_release --codename --short
111s + RELEASE=plucky
111s + cat
111s + [ plucky != trusty ]
111s + DEBIAN_FRONTEND=noninteractive eatmydata apt-get -y --allow-downgrades -o Dpkg::Options::=--force-confnew dist-upgrade
111s Reading package lists...
111s Building dependency tree...
111s Reading state information...
112s Calculating upgrade...
112s Calculating upgrade...
112s The following packages were automatically installed and are no longer required:
112s   libnsl2 libpython3.12-minimal libpython3.12-stdlib libpython3.12t64
112s   linux-headers-6.11.0-8 linux-headers-6.11.0-8-generic
112s   linux-modules-6.11.0-8-generic linux-tools-6.11.0-8
112s   linux-tools-6.11.0-8-generic
112s Use 'sudo apt autoremove' to remove them.
112s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
112s + rm /etc/apt/preferences.d/force-downgrade-to-release.pref
112s + /usr/lib/apt/apt-helper analyze-pattern ?true
112s + uname -r
112s + sed s/\./\\./g
112s + running_kernel_pattern=^linux-.*6\.12\.0-15-generic.*
112s + apt list ?obsolete
112s + tail -n+2
112s + cut -d/ -f1
112s + grep -v ^linux-.*6\.12\.0-15-generic.*
112s + true
112s + obsolete_pkgs=
112s + DEBIAN_FRONTEND=noninteractive eatmydata apt-get -y purge --autoremove
112s Reading package lists...
112s Building dependency tree...
112s Reading state information...
112s Solving dependencies...
112s The following packages will be REMOVED:
112s   libnsl2* libpython3.12-minimal* libpython3.12-stdlib* libpython3.12t64*
112s   linux-headers-6.11.0-8* linux-headers-6.11.0-8-generic*
112s   linux-modules-6.11.0-8-generic* linux-tools-6.11.0-8*
112s   linux-tools-6.11.0-8-generic*
113s 0 upgraded, 0 newly installed, 9 to remove and 3 not upgraded.
113s After this operation, 167 MB disk space will be freed.
113s (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 ... 81030 files and directories currently installed.)
113s Removing linux-tools-6.11.0-8-generic (6.11.0-8.8) ...
113s Removing linux-tools-6.11.0-8 (6.11.0-8.8) ...
113s Removing libpython3.12t64:s390x (3.12.9-1) ...
113s Removing libpython3.12-stdlib:s390x (3.12.9-1) ...
113s Removing libnsl2:s390x (1.3.0-3build3) ...
113s Removing libpython3.12-minimal:s390x (3.12.9-1) ...
113s Removing linux-headers-6.11.0-8-generic (6.11.0-8.8) ...
113s Removing linux-headers-6.11.0-8 (6.11.0-8.8) ...
114s Removing linux-modules-6.11.0-8-generic (6.11.0-8.8) ...
114s Processing triggers for libc-bin (2.40-4ubuntu1) ...
114s (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 ... 55930 files and directories currently installed.)
114s Purging configuration files for libpython3.12-minimal:s390x (3.12.9-1) ...
114s Purging configuration files for linux-modules-6.11.0-8-generic (6.11.0-8.8) ...
114s + grep -q trusty /etc/lsb-release
114s + [ ! -d /usr/share/doc/unattended-upgrades ]
114s + [ ! -d /usr/share/doc/lxd ]
114s + [ ! -d /usr/share/doc/lxd-client ]
114s + [ ! -d /usr/share/doc/snapd ]
114s + type iptables
114s + cat
114s + chmod 755 /etc/rc.local
114s + . /etc/rc.local
114s + iptables -w -t mangle -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
114s + iptables -A OUTPUT -d 10.255.255.1/32 -p tcp -j DROP
114s + iptables -A OUTPUT -d 10.255.255.2/32 -p tcp -j DROP
114s + uname -m
114s + [ s390x = ppc64le ]
114s + [ -d /run/systemd/system ]
114s + systemd-detect-virt --quiet --vm
114s + mkdir -p /etc/systemd/system/systemd-random-seed.service.d/
114s + cat
114s + grep -q lz4 /etc/initramfs-tools/initramfs.conf
114s + echo COMPRESS=lz4
114s autopkgtest [05:02:05]: upgrading testbed (apt dist-upgrade and autopurge)
114s Reading package lists...
115s Building dependency tree...
115s Reading state information...
115s Calculating upgrade...Starting pkgProblemResolver with broken count: 0
115s Starting 2 pkgProblemResolver with broken count: 0
115s Done
115s Entering ResolveByKeep
115s 
115s Calculating upgrade...
115s The following packages will be upgraded:
115s   gir1.2-glib-2.0 libglib2.0-0t64 libglib2.0-data
115s 3 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
115s Need to get 1819 kB of archives.
115s After this operation, 1024 B disk space will be freed.
115s Get:1 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x gir1.2-glib-2.0 s390x 2.83.4-1 [182 kB]
116s Get:2 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x libglib2.0-0t64 s390x 2.83.4-1 [1584 kB]
116s Get:3 http://ftpmaster.internal/ubuntu plucky-proposed/main s390x libglib2.0-data all 2.83.4-1 [52.9 kB]
116s Fetched 1819 kB in 1s (3004 kB/s)
116s (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 ... 55928 files and directories currently installed.)
116s Preparing to unpack .../gir1.2-glib-2.0_2.83.4-1_s390x.deb ...
116s Unpacking gir1.2-glib-2.0:s390x (2.83.4-1) over (2.83.3-2) ...
116s Preparing to unpack .../libglib2.0-0t64_2.83.4-1_s390x.deb ...
116s Unpacking libglib2.0-0t64:s390x (2.83.4-1) over (2.83.3-2) ...
116s Preparing to unpack .../libglib2.0-data_2.83.4-1_all.deb ...
116s Unpacking libglib2.0-data (2.83.4-1) over (2.83.3-2) ...
116s Setting up libglib2.0-0t64:s390x (2.83.4-1) ...
116s No schema files found: doing nothing.
116s Setting up libglib2.0-data (2.83.4-1) ...
116s Setting up gir1.2-glib-2.0:s390x (2.83.4-1) ...
116s Processing triggers for libc-bin (2.40-4ubuntu1) ...
117s Reading package lists...
117s Building dependency tree...
117s Reading state information...
117s Starting pkgProblemResolver with broken count: 0
117s Starting 2 pkgProblemResolver with broken count: 0
117s Done
117s Solving dependencies...
117s 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
117s autopkgtest [05:02:08]: rebooting testbed after setup commands that affected boot
135s autopkgtest [05:02:26]: testbed running kernel: Linux 6.12.0-15-generic #15-Ubuntu SMP Tue Feb  4 15:05:57 UTC 2025
137s autopkgtest [05:02:28]: @@@@@@@@@@@@@@@@@@@@ apt-source libfprint
142s Get:1 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.9+tod1-1 (dsc) [2943 B]
142s Get:2 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.9+tod1-1 (tar) [9291 kB]
142s Get:3 http://ftpmaster.internal/ubuntu plucky/main libfprint 1:1.94.9+tod1-1 (diff) [17.8 kB]
142s gpgv: Signature made Thu Feb 20 18:31:16 2025 UTC
142s gpgv:                using RSA key D4C501DA48EB797A081750939449C2F50996635F
142s gpgv: Can't check signature: No public key
142s dpkg-source: warning: cannot verify inline signature for ./libfprint_1.94.9+tod1-1.dsc: no acceptable signature found
143s autopkgtest [05:02:34]: testing package libfprint version 1:1.94.9+tod1-1
144s autopkgtest [05:02:35]: build not needed
146s autopkgtest [05:02:37]: test installed-tests: preparing testbed
147s Reading package lists...
147s Building dependency tree...
147s Reading state information...
147s Starting pkgProblemResolver with broken count: 0
147s Starting 2 pkgProblemResolver with broken count: 0
147s Done
147s The following NEW packages will be installed:
147s   fontconfig-config fonts-dejavu-core fonts-dejavu-mono gir1.2-fprint-2.0
147s   gir1.2-gusb-1.0 gir1.2-json-1.0 gnome-desktop-testing libcairo2
147s   libfontconfig1 libfprint-2-2 libfprint-2-tests libfprint-2-tod1 libfreetype6
147s   libgusb2 libpixman-1-0 libumockdev0 libxcb-render0 libxcb-shm0 libxrender1
147s   python3-cairo umockdev
147s 0 upgraded, 21 newly installed, 0 to remove and 0 not upgraded.
147s Need to get 5353 kB of archives.
147s After this operation, 15.5 MB of additional disk space will be used.
147s Get:1 http://ftpmaster.internal/ubuntu plucky/main s390x fonts-dejavu-mono all 2.37-8 [502 kB]
148s Get:2 http://ftpmaster.internal/ubuntu plucky/main s390x fonts-dejavu-core all 2.37-8 [835 kB]
148s Get:3 http://ftpmaster.internal/ubuntu plucky/main s390x fontconfig-config s390x 2.15.0-2ubuntu1 [37.5 kB]
148s Get:4 http://ftpmaster.internal/ubuntu plucky/main s390x gir1.2-json-1.0 s390x 1.10.6+ds-1 [9920 B]
148s Get:5 http://ftpmaster.internal/ubuntu plucky/main s390x libgusb2 s390x 0.4.9-1 [38.9 kB]
148s Get:6 http://ftpmaster.internal/ubuntu plucky/main s390x gir1.2-gusb-1.0 s390x 0.4.9-1 [7370 B]
148s Get:7 http://ftpmaster.internal/ubuntu plucky/main s390x libpixman-1-0 s390x 0.44.0-3 [201 kB]
148s Get:8 http://ftpmaster.internal/ubuntu plucky/main s390x libfprint-2-tod1 s390x 1:1.94.9+tod1-1 [65.7 kB]
148s Get:9 http://ftpmaster.internal/ubuntu plucky/main s390x libfprint-2-2 s390x 1:1.94.9+tod1-1 [204 kB]
148s Get:10 http://ftpmaster.internal/ubuntu plucky/main s390x gir1.2-fprint-2.0 s390x 1:1.94.9+tod1-1 [7174 B]
148s Get:11 http://ftpmaster.internal/ubuntu plucky/universe s390x gnome-desktop-testing s390x 2021.1-4 [16.6 kB]
148s Get:12 http://ftpmaster.internal/ubuntu plucky/main s390x libfreetype6 s390x 2.13.3+dfsg-1 [431 kB]
148s Get:13 http://ftpmaster.internal/ubuntu plucky/main s390x libfontconfig1 s390x 2.15.0-2ubuntu1 [150 kB]
148s Get:14 http://ftpmaster.internal/ubuntu plucky/main s390x libxcb-render0 s390x 1.17.0-2 [17.0 kB]
148s Get:15 http://ftpmaster.internal/ubuntu plucky/main s390x libxcb-shm0 s390x 1.17.0-2 [5862 B]
148s Get:16 http://ftpmaster.internal/ubuntu plucky/main s390x libxrender1 s390x 1:0.9.10-1.1build1 [20.4 kB]
148s Get:17 http://ftpmaster.internal/ubuntu plucky/main s390x libcairo2 s390x 1.18.2-2 [580 kB]
148s Get:18 http://ftpmaster.internal/ubuntu plucky/main s390x python3-cairo s390x 1.26.1-2build1 [138 kB]
148s Get:19 http://ftpmaster.internal/ubuntu plucky/universe s390x libumockdev0 s390x 0.19.1-3 [77.1 kB]
148s Get:20 http://ftpmaster.internal/ubuntu plucky/universe s390x umockdev s390x 0.19.1-3 [75.1 kB]
148s Get:21 http://ftpmaster.internal/ubuntu plucky/universe s390x libfprint-2-tests s390x 1:1.94.9+tod1-1 [1933 kB]
148s Fetched 5353 kB in 1s (6374 kB/s)
148s Selecting previously unselected package fonts-dejavu-mono.
148s (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 ... 55928 files and directories currently installed.)
148s Preparing to unpack .../00-fonts-dejavu-mono_2.37-8_all.deb ...
148s Unpacking fonts-dejavu-mono (2.37-8) ...
148s Selecting previously unselected package fonts-dejavu-core.
148s Preparing to unpack .../01-fonts-dejavu-core_2.37-8_all.deb ...
148s Unpacking fonts-dejavu-core (2.37-8) ...
148s Selecting previously unselected package fontconfig-config.
148s Preparing to unpack .../02-fontconfig-config_2.15.0-2ubuntu1_s390x.deb ...
148s Unpacking fontconfig-config (2.15.0-2ubuntu1) ...
148s Selecting previously unselected package gir1.2-json-1.0:s390x.
148s Preparing to unpack .../03-gir1.2-json-1.0_1.10.6+ds-1_s390x.deb ...
148s Unpacking gir1.2-json-1.0:s390x (1.10.6+ds-1) ...
148s Selecting previously unselected package libgusb2:s390x.
148s Preparing to unpack .../04-libgusb2_0.4.9-1_s390x.deb ...
148s Unpacking libgusb2:s390x (0.4.9-1) ...
148s Selecting previously unselected package gir1.2-gusb-1.0:s390x.
148s Preparing to unpack .../05-gir1.2-gusb-1.0_0.4.9-1_s390x.deb ...
148s Unpacking gir1.2-gusb-1.0:s390x (0.4.9-1) ...
148s Selecting previously unselected package libpixman-1-0:s390x.
148s Preparing to unpack .../06-libpixman-1-0_0.44.0-3_s390x.deb ...
148s Unpacking libpixman-1-0:s390x (0.44.0-3) ...
148s Selecting previously unselected package libfprint-2-tod1:s390x.
148s Preparing to unpack .../07-libfprint-2-tod1_1%3a1.94.9+tod1-1_s390x.deb ...
148s Unpacking libfprint-2-tod1:s390x (1:1.94.9+tod1-1) ...
149s Selecting previously unselected package libfprint-2-2.
149s Preparing to unpack .../08-libfprint-2-2_1%3a1.94.9+tod1-1_s390x.deb ...
149s Unpacking libfprint-2-2 (1:1.94.9+tod1-1) ...
149s Selecting previously unselected package gir1.2-fprint-2.0:s390x.
149s Preparing to unpack .../09-gir1.2-fprint-2.0_1%3a1.94.9+tod1-1_s390x.deb ...
149s Unpacking gir1.2-fprint-2.0:s390x (1:1.94.9+tod1-1) ...
149s Selecting previously unselected package gnome-desktop-testing.
149s Preparing to unpack .../10-gnome-desktop-testing_2021.1-4_s390x.deb ...
149s Unpacking gnome-desktop-testing (2021.1-4) ...
149s Selecting previously unselected package libfreetype6:s390x.
149s Preparing to unpack .../11-libfreetype6_2.13.3+dfsg-1_s390x.deb ...
149s Unpacking libfreetype6:s390x (2.13.3+dfsg-1) ...
149s Selecting previously unselected package libfontconfig1:s390x.
149s Preparing to unpack .../12-libfontconfig1_2.15.0-2ubuntu1_s390x.deb ...
149s Unpacking libfontconfig1:s390x (2.15.0-2ubuntu1) ...
149s Selecting previously unselected package libxcb-render0:s390x.
149s Preparing to unpack .../13-libxcb-render0_1.17.0-2_s390x.deb ...
149s Unpacking libxcb-render0:s390x (1.17.0-2) ...
149s Selecting previously unselected package libxcb-shm0:s390x.
149s Preparing to unpack .../14-libxcb-shm0_1.17.0-2_s390x.deb ...
149s Unpacking libxcb-shm0:s390x (1.17.0-2) ...
149s Selecting previously unselected package libxrender1:s390x.
149s Preparing to unpack .../15-libxrender1_1%3a0.9.10-1.1build1_s390x.deb ...
149s Unpacking libxrender1:s390x (1:0.9.10-1.1build1) ...
149s Selecting previously unselected package libcairo2:s390x.
149s Preparing to unpack .../16-libcairo2_1.18.2-2_s390x.deb ...
149s Unpacking libcairo2:s390x (1.18.2-2) ...
149s Selecting previously unselected package python3-cairo.
149s Preparing to unpack .../17-python3-cairo_1.26.1-2build1_s390x.deb ...
149s Unpacking python3-cairo (1.26.1-2build1) ...
149s Selecting previously unselected package libumockdev0:s390x.
149s Preparing to unpack .../18-libumockdev0_0.19.1-3_s390x.deb ...
149s Unpacking libumockdev0:s390x (0.19.1-3) ...
149s Selecting previously unselected package umockdev.
149s Preparing to unpack .../19-umockdev_0.19.1-3_s390x.deb ...
149s Unpacking umockdev (0.19.1-3) ...
149s Selecting previously unselected package libfprint-2-tests.
149s Preparing to unpack .../20-libfprint-2-tests_1%3a1.94.9+tod1-1_s390x.deb ...
149s Unpacking libfprint-2-tests (1:1.94.9+tod1-1) ...
149s Setting up gnome-desktop-testing (2021.1-4) ...
149s Setting up libpixman-1-0:s390x (0.44.0-3) ...
149s Setting up libxrender1:s390x (1:0.9.10-1.1build1) ...
149s Setting up libxcb-render0:s390x (1.17.0-2) ...
149s Setting up libgusb2:s390x (0.4.9-1) ...
149s Setting up libfprint-2-tod1:s390x (1:1.94.9+tod1-1) ...
149s Setting up libxcb-shm0:s390x (1.17.0-2) ...
149s Setting up libfreetype6:s390x (2.13.3+dfsg-1) ...
149s Setting up fonts-dejavu-mono (2.37-8) ...
149s Setting up fonts-dejavu-core (2.37-8) ...
149s Setting up libumockdev0:s390x (0.19.1-3) ...
149s Setting up gir1.2-json-1.0:s390x (1.10.6+ds-1) ...
149s Setting up libfprint-2-2 (1:1.94.9+tod1-1) ...
151s Setting up umockdev (0.19.1-3) ...
151s Setting up fontconfig-config (2.15.0-2ubuntu1) ...
151s Setting up gir1.2-gusb-1.0:s390x (0.4.9-1) ...
151s Setting up libfontconfig1:s390x (2.15.0-2ubuntu1) ...
151s Setting up gir1.2-fprint-2.0:s390x (1:1.94.9+tod1-1) ...
151s Setting up libcairo2:s390x (1.18.2-2) ...
151s Setting up python3-cairo (1.26.1-2build1) ...
151s Setting up libfprint-2-tests (1:1.94.9+tod1-1) ...
151s Processing triggers for man-db (2.13.0-1) ...
151s Processing triggers for udev (257.2-3ubuntu1) ...
152s Processing triggers for libc-bin (2.40-4ubuntu1) ...
153s autopkgtest [05:02:44]: test installed-tests: gnome-desktop-testing-runner libfprint-2
153s autopkgtest [05:02:44]: test installed-tests: [-----------------------
153s Running test: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test
153s TAP version 14
153s # random seed: R02S90cde4f80fca24f062172401012541cf
153s 1..4
153s # Start of context tests
153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffb2f82990, GType is 2929694233792
153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
153s ok 1 /context/new
153s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
153s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
153s ok 2 /context/no-devices
153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffb2f82990, GType is 2929694233792
153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
153s # libfprint-context-DEBUG: created
153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
153s # 
153s # libfprint-device-DEBUG: Device reported probe completion
153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
153s # 
153s # libfprint-device-DEBUG: Device reported open completion
153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
153s # 
153s # libfprint-device-DEBUG: Device reported close completion
153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
153s ok 3 /context/has-virtual-device
153s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
153s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
153s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffb2f82990, GType is 2929694233792
153s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
153s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
153s # libfprint-context-DEBUG: created
153s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
153s # 
153s # libfprint-device-DEBUG: Device reported probe completion
153s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
153s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
153s ok 4 /context/enumerates-new-devices
153s # End of context tests
153s PASS: libfprint-2/tod-fp-context-tod-fake_test_dev_tod_current.test
153s Running test: libfprint-2/driver-upektc_img-tcs1s.test
153s ** (umockdev-run:2339): DEBUG: 05:04:10.107: umockdev.vala:127: Created udev test bed /tmp/umockdev.5YAC22
153s ** (umockdev-run:2339): DEBUG: 05:04:10.107: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2
153s ** (umockdev-run:2339): DEBUG: 05:04:10.111: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-2 (subsystem usb)
153s ** (umockdev-run:2339): DEBUG: 05:04:10.112: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.5YAC22/dev/bus/usb/003/004
153s ** (umockdev-run:2339): DEBUG: 05:04:10.112: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3
153s ** (umockdev-run:2339): DEBUG: 05:04:10.116: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3 (subsystem usb)
153s ** (umockdev-run:2339): DEBUG: 05:04:10.117: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.5YAC22/dev/bus/usb/003/001
153s ** (umockdev-run:2339): DEBUG: 05:04:10.117: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1/0000:05:00.4
153s ** (umockdev-run:2339): DEBUG: 05:04:10.119: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1/0000:05:00.4 (subsystem pci)
153s ** (umockdev-run:2339): DEBUG: 05:04:10.120: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:08.1
153s ** (umockdev-run:2339): DEBUG: 05:04:10.121: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:08.1 (subsystem pci)
153s (process:2343): libfprint-context-DEBUG: 05:04:10.198: Initializing FpContext (libfprint version 1.94.9+tod1)
153s (process:2343): libfprint-tod-DEBUG: 05:04:10.198: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
153s (process:2343): libfprint-context-DEBUG: 05:04:10.199: No driver found for USB device 1D6B:0002
153s (process:2343): libfprint-device-DEBUG: 05:04:10.199: Device reported probe completion
153s (process:2343): libfprint-device-DEBUG: 05:04:10.199: Completing action FPI_DEVICE_ACTION_PROBE in idle!
153s (process:2343): libfprint-device-DEBUG: 05:04:10.199: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.200: Image device open completed
153s (process:2343): libfprint-device-DEBUG: 05:04:10.200: Device reported open completion
153s (process:2343): libfprint-device-DEBUG: 05:04:10.200: Completing action FPI_DEVICE_ACTION_OPEN in idle!
153s (process:2343): libfprint-device-DEBUG: 05:04:10.200: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
153s (process:2343): libfprint-device-DEBUG: 05:04:10.200: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.200: Activating image device
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.200: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.200: [upektc_img] ACTIVATE_NUM_STATES entering state 0
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.201: [upektc_img] ACTIVATE_NUM_STATES entering state 1
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.201: [upektc_img] ACTIVATE_NUM_STATES entering state 2
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.201: [upektc_img] ACTIVATE_NUM_STATES entering state 3
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.201: [upektc_img] ACTIVATE_NUM_STATES entering state 4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.202: [upektc_img] ACTIVATE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.202: [upektc_img] ACTIVATE_NUM_STATES entering state 6
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.202: [upektc_img] ACTIVATE_NUM_STATES entering state 7
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.203: [upektc_img] ACTIVATE_NUM_STATES entering state 8
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.203: [upektc_img] ACTIVATE_NUM_STATES entering state 9
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.203: [upektc_img] ACTIVATE_NUM_STATES entering state 10
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.203: [upektc_img] ACTIVATE_NUM_STATES entering state 11
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.204: Sensor type : TCS1x, width x height: 256 x 360
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.204: [upektc_img] ACTIVATE_NUM_STATES completed successfully
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.204: Image device activation completed
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.204: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.204: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
153s (process:2343): libfprint-device-DEBUG: 05:04:10.204: Device reported finger status change: FP_FINGER_STATUS_NEEDED
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.204: [upektc_img] CAPTURE_NUM_STATES entering state 0
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.204: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.204: request completed, len: 0000
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.204: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.205: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.205: 18th byte is 0c
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.205: [upektc_img] CAPTURE_NUM_STATES entering state 3
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.205: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.205: request completed, len: 0000
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.205: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.206: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.206: 18th byte is 13
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.206: [upektc_img] CAPTURE_NUM_STATES entering state 3
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.206: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.206: request completed, len: 0000
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.206: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.207: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.207: 18th byte is 00
153s (process:2343): libfprint-device-DEBUG: 05:04:10.207: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.207: [upektc_img] CAPTURE_NUM_STATES entering state 3
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.207: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.207: request completed, len: 0000
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.207: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.207: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.207: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.207: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.207: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.208: request completed, len: 07c4
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.208: Image device reported finger status: on
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.208: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.208: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.208: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.208: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.208: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.208: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.208: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.209: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.209: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.209: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.209: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.209: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.209: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.209: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.210: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.210: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.210: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.210: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.210: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.210: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.210: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.211: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.211: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.211: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.211: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.211: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.211: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.211: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.212: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.212: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.212: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.212: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.212: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.212: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.212: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.212: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.212: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.213: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.213: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.213: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.213: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.213: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.213: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.213: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.214: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.214: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.214: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.214: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.214: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.214: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.214: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.215: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.215: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.215: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.215: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.215: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.215: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.215: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.216: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.216: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.216: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.216: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.216: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.216: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.216: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.217: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.217: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.217: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.217: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.217: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.217: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.217: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.218: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.218: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.218: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.218: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.218: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.218: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.218: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.218: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.219: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.219: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.219: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.219: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.219: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.219: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.219: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.220: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.220: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.220: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.220: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.220: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.220: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.220: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.221: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.221: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.221: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.221: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.221: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.221: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.221: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.221: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.221: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.221: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.221: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.222: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.222: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.222: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.222: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.222: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.222: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.222: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.222: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.222: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.223: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.223: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.223: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.223: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.223: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.223: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.223: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.224: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.224: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.224: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.224: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.224: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.224: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.224: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.225: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.225: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.225: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.225: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.225: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.226: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.226: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.226: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.226: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.226: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.226: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.226: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.226: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.227: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.227: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.227: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.227: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.227: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.227: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.227: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.227: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.228: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.228: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.228: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.228: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.228: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.229: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.229: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.229: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.229: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.229: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.229: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.229: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.229: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.229: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.230: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.230: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.230: response_size is 2052, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.230: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.230: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.230: request completed, len: 07c4
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.230: [upektc_img] CAPTURE_NUM_STATES entering state 5
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.231: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.231: request completed, len: 0040
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.231: response_size is 814, actual_length is 64
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.231: Waiting for rest of transfer
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.231: [upektc_img] CAPTURE_NUM_STATES entering state 1
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.231: request completed, len: 02ee
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.231: Image size is 51840
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.231: Image device captured an image
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.231: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
153s (process:2343): libfprint-device-DEBUG: 05:04:10.231: Device reported finger status change: FP_FINGER_STATUS_PRESENT
153s (process:2343): libfprint-device-DEBUG: 05:04:10.231: Device reported finger status change: FP_FINGER_STATUS_NONE
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.231: Image device reported finger status: off
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.231: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.231: Deactivating image device
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.231: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.231: [upektc_img] CAPTURE_NUM_STATES completed successfully
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.231: [upektc_img] DEACTIVATE_NUM_STATES entering state 0
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.235: [upektc_img] DEACTIVATE_NUM_STATES entering state 1
153s (process:2343): libfprint-SSM-DEBUG: 05:04:10.235: [upektc_img] DEACTIVATE_NUM_STATES completed successfully
153s (process:2343): libfprint-upektc_img-DEBUG: 05:04:10.235: Deactivate completed
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.235: Image device deactivation completed
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.235: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
153s (process:2343): libfprint-image-DEBUG: 05:04:10.252: Minutiae scan completed in 0.020225 secs
153s (process:2343): libfprint-device-DEBUG: 05:04:10.252: Device reported capture completion
153s (process:2343): libfprint-device-DEBUG: 05:04:10.252: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
153s (process:2343): libfprint-device-DEBUG: 05:04:10.252: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
153s (process:2343): libfprint-image_device-DEBUG: 05:04:10.252: Image device close completed
153s (process:2343): libfprint-device-DEBUG: 05:04:10.252: Device reported close completion
153s (process:2343): libfprint-device-DEBUG: 05:04:10.252: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
153s (process:2343): libfprint-device-DEBUG: 05:04:10.252: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
153s ** (umockdev-run:2339): DEBUG: 05:04:10.333: umockdev.vala:154: Removing test bed /tmp/umockdev.5YAC22
153s (umockdev-run:2339): GLib-DEBUG: 05:04:10.336: unsetenv() is not thread-safe and should not be used after threads are created
153s Comparing PNGs /tmp/libfprint-umockdev-test-jb1_gedo/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img-tcs1s/capture.png
153s PASS: libfprint-2/driver-upektc_img-tcs1s.test
153s Running test: libfprint-2/virtual-image.test
153s (process:2350): libfprint-context-DEBUG: 05:04:10.439: Initializing FpContext (libfprint version 1.94.9+tod1)
153s (process:2350): libfprint-tod-DEBUG: 05:04:10.439: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
153s (process:2350): libfprint-context-DEBUG: 05:04:10.439: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-j5cybx12/virtual-image.socket
153s (process:2350): libfprint-context-DEBUG: 05:04:10.440: created
153s (process:2350): libfprint-device-DEBUG: 05:04:10.440: Device reported probe completion
153s (process:2350): libfprint-device-DEBUG: 05:04:10.440: Completing action FPI_DEVICE_ACTION_PROBE in idle!
153s (process:2350): libfprint-device-DEBUG: 05:04:10.440: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
153s test_capture_prevents_close (__main__.VirtualImage.test_capture_prevents_close) ... (process:2350): libfprint-virtual_image-DEBUG: 05:04:10.445: 31520922: ../libfprint/drivers/virtual-image.c:216
153s (process:2350): libfprint-virtual_device_connection-DEBUG: 05:04:10.446: 31520975: ../libfprint/drivers/virtual-device-listener.c:153
153s (process:2350): libfprint-image_device-DEBUG: 05:04:10.546: Image device open completed
153s (process:2350): libfprint-device-DEBUG: 05:04:10.546: Device reported open completion
153s (process:2350): libfprint-device-DEBUG: 05:04:10.546: Completing action FPI_DEVICE_ACTION_OPEN in idle!
153s (process:2350): libfprint-device-DEBUG: 05:04:10.546: Updated temperature model after 0.11 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
153s (process:2350): libfprint-device-DEBUG: 05:04:10.547: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
153s (process:2350): libfprint-image_device-DEBUG: 05:04:10.547: Activating image device
153s (process:2350): libfprint-image_device-DEBUG: 05:04:10.547: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
153s (process:2350): libfprint-image_device-DEBUG: 05:04:10.547: Image device activation completed
153s (process:2350): libfprint-image_device-DEBUG: 05:04:10.547: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
153s (process:2350): libfprint-image_device-DEBUG: 05:04:10.547: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
153s (process:2350): libfprint-device-DEBUG: 05:04:10.547: Device reported finger status change: FP_FINGER_STATUS_NEEDED
153s (process:2350): libfprint-virtual_device_connection-DEBUG: 05:04:10.547: Got a new connection!
153s (process:2350): libfprint-device-DEBUG: 05:04:10.547: Idle cancelling on ongoing operation!
153s (process:2350): libfprint-image_device-DEBUG: 05:04:10.547: Deactivating image device
153s (process:2350): libfprint-image_device-DEBUG: 05:04:10.547: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
153s (process:2350): libfprint-image_device-DEBUG: 05:04:10.547: Image device deactivation completed
153s (process:2350): libfprint-image_device-DEBUG: 05:04:10.547: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
153s (process:2350): libfprint-device-DEBUG: 05:04:10.547: Device reported generic error (Operation was cancelled) during action; action was: FPI_DEVICE_ACTION_CAPTURE
153s (process:2350): libfprint-device-DEBUG: 05:04:10.547: Device reported capture completion
153s (process:2350): libfprint-device-DEBUG: 05:04:10.547: Device reported finger status change: FP_FINGER_STATUS_NONE
153s (process:2350): libfprint-device-DEBUG: 05:04:10.547: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
153s (process:2350): libfprint-device-DEBUG: 05:04:10.547: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
153s (process:2350): libfprint-virtual_image-DEBUG: 05:04:10.548: 31623102: ../libfprint/drivers/virtual-image.c:244
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.648: Image device close completed
154s (process:2350): libfprint-device-DEBUG: 05:04:10.648: Device reported close completion
154s (process:2350): libfprint-device-DEBUG: 05:04:10.648: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
154s (process:2350): libfprint-device-DEBUG: 05:04:10.648: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
154s Capture operation finished
154s Capture cancelled as expected
154s ok
154s test_enroll_verify (__main__.VirtualImage.test_enroll_verify) ... (process:2350): libfprint-virtual_image-DEBUG: 05:04:10.648: 31723686: ../libfprint/drivers/virtual-image.c:216
154s (process:2350): libfprint-virtual_device_connection-DEBUG: 05:04:10.648: 31723706: ../libfprint/drivers/virtual-device-listener.c:153
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.748: Image device open completed
154s (process:2350): libfprint-device-DEBUG: 05:04:10.748: Device reported open completion
154s (process:2350): libfprint-device-DEBUG: 05:04:10.748: Completing action FPI_DEVICE_ACTION_OPEN in idle!
154s (process:2350): libfprint-device-DEBUG: 05:04:10.748: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
154s (process:2350): libfprint-device-DEBUG: 05:04:10.749: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.750: Activating image device
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.750: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.750: Image device activation completed
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.750: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.750: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
154s (process:2350): libfprint-device-DEBUG: 05:04:10.750: Device reported finger status change: FP_FINGER_STATUS_NEEDED
154s (process:2350): libfprint-virtual_device_connection-DEBUG: 05:04:10.750: Got a new connection!
154s (process:2350): libfprint-virtual_image-DEBUG: 05:04:10.750: image data: 0x31ad5e0
154s (process:2350): libfprint-device-DEBUG: 05:04:10.750: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.750: Image device reported finger status: on
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.750: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.750: Image device captured an image
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.750: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
154s (process:2350): libfprint-device-DEBUG: 05:04:10.750: Device reported finger status change: FP_FINGER_STATUS_PRESENT
154s (process:2350): libfprint-device-DEBUG: 05:04:10.750: Device reported finger status change: FP_FINGER_STATUS_NONE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.755: Image device reported finger status: off
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.755: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
154s (process:2350): libfprint-image-DEBUG: 05:04:10.776: Minutiae scan completed in 0.026262 secs
154s (process:2350): libfprint-device-DEBUG: 05:04:10.777: Device reported enroll progress, reported 1 of 5 have been completed
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.777: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
154s (process:2350): libfprint-device-DEBUG: 05:04:10.777: Device reported finger status change: FP_FINGER_STATUS_NEEDED
154s (process:2350): libfprint-device-DEBUG: 05:04:10.777: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.777: Image device reported finger status: on
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.777: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
154s (process:2350): libfprint-virtual_image-DEBUG: 05:04:10.777: image data: 0x31bbe40
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.777: Image device captured an image
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.777: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
154s (process:2350): libfprint-device-DEBUG: 05:04:10.777: Device reported finger status change: FP_FINGER_STATUS_PRESENT
154s (process:2350): libfprint-image-DEBUG: 05:04:10.802: Minutiae scan completed in 0.025707 secs
154s (process:2350): libfprint-device-DEBUG: 05:04:10.803: Device reported enroll progress, reported 2 of 5 have been completed
154s (process:2350): libfprint-device-DEBUG: 05:04:10.803: Device reported finger status change: FP_FINGER_STATUS_NONE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.803: Image device reported finger status: off
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
154s (process:2350): libfprint-device-DEBUG: 05:04:10.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED
154s (process:2350): libfprint-virtual_image-DEBUG: 05:04:10.803: image data: 0x31ad5e0
154s (process:2350): libfprint-device-DEBUG: 05:04:10.803: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.803: Image device reported finger status: on
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.803: Image device captured an image
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
154s (process:2350): libfprint-device-DEBUG: 05:04:10.803: Device reported finger status change: FP_FINGER_STATUS_PRESENT
154s (process:2350): libfprint-device-DEBUG: 05:04:10.803: Device reported finger status change: FP_FINGER_STATUS_NONE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.803: Image device reported finger status: off
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.803: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
154s (process:2350): libfprint-image-DEBUG: 05:04:10.828: Minutiae scan completed in 0.025645 secs
154s (process:2350): libfprint-device-DEBUG: 05:04:10.828: Device reported enroll progress, reported 3 of 5 have been completed
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.829: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
154s (process:2350): libfprint-device-DEBUG: 05:04:10.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED
154s (process:2350): libfprint-virtual_image-DEBUG: 05:04:10.829: image data: 0x31ad5e0
154s (process:2350): libfprint-device-DEBUG: 05:04:10.829: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.829: Image device reported finger status: on
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.829: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.829: Image device captured an image
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.829: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
154s (process:2350): libfprint-device-DEBUG: 05:04:10.829: Device reported finger status change: FP_FINGER_STATUS_PRESENT
154s (process:2350): libfprint-device-DEBUG: 05:04:10.829: Device reported finger status change: FP_FINGER_STATUS_NONE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.829: Image device reported finger status: off
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.829: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
154s (process:2350): libfprint-image-DEBUG: 05:04:10.854: Minutiae scan completed in 0.025755 secs
154s (process:2350): libfprint-device-DEBUG: 05:04:10.854: Device reported enroll progress, reported 4 of 5 have been completed
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.855: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
154s (process:2350): libfprint-device-DEBUG: 05:04:10.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED
154s (process:2350): libfprint-virtual_image-DEBUG: 05:04:10.855: image data: 0x31bbe60
154s (process:2350): libfprint-device-DEBUG: 05:04:10.855: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.855: Image device reported finger status: on
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.855: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.855: Image device captured an image
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.855: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
154s (process:2350): libfprint-device-DEBUG: 05:04:10.855: Device reported finger status change: FP_FINGER_STATUS_PRESENT
154s (process:2350): libfprint-device-DEBUG: 05:04:10.855: Device reported finger status change: FP_FINGER_STATUS_NONE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.855: Image device reported finger status: off
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.855: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
154s (process:2350): libfprint-image-DEBUG: 05:04:10.880: Minutiae scan completed in 0.025576 secs
154s (process:2350): libfprint-device-DEBUG: 05:04:10.880: Device reported enroll progress, reported 5 of 5 have been completed
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.880: Deactivating image device
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.880: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.880: Image device deactivation completed
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.880: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
154s (process:2350): libfprint-device-DEBUG: 05:04:10.880: Device reported enroll completion
154s (process:2350): libfprint-device-DEBUG: 05:04:10.880: Print for finger FP_FINGER_LEFT_THUMB enrolled
154s (process:2350): libfprint-device-DEBUG: 05:04:10.880: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
154s (process:2350): libfprint-device-DEBUG: 05:04:10.880: Updated temperature model after 0.13 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
154s (process:2350): libfprint-device-DEBUG: 05:04:10.881: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Activating image device
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Image device activation completed
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
154s (process:2350): libfprint-device-DEBUG: 05:04:10.881: Device reported finger status change: FP_FINGER_STATUS_NEEDED
154s (process:2350): libfprint-virtual_image-DEBUG: 05:04:10.881: image data: 0x31bbe60
154s (process:2350): libfprint-device-DEBUG: 05:04:10.881: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Image device reported finger status: on
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Image device captured an image
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
154s (process:2350): libfprint-device-DEBUG: 05:04:10.881: Device reported finger status change: FP_FINGER_STATUS_PRESENT
154s (process:2350): libfprint-device-DEBUG: 05:04:10.881: Device reported finger status change: FP_FINGER_STATUS_NONE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Image device reported finger status: off
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Deactivating image device
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Image device deactivation completed
154s (process:2350): libfprint-image_device-DEBUG: 05:04:10.881: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
154s (process:2350): libfprint-image-DEBUG: 05:04:10.907: Minutiae scan completed in 0.025665 secs
155s (process:2350): libfprint-print-DEBUG: 05:04:12.021: score 1093/40
155s (process:2350): libfprint-device-DEBUG: 05:04:12.021: Device reported verify result
155s (process:2350): libfprint-device-DEBUG: 05:04:12.021: Device reported verify completion
155s (process:2350): libfprint-device-DEBUG: 05:04:12.021: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
155s (process:2350): libfprint-device-DEBUG: 05:04:12.021: Updated temperature model after 1.14 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
155s (process:2350): libfprint-device-DEBUG: 05:04:12.021: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.021: Activating image device
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.021: Image device activation completed
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.021: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
155s (process:2350): libfprint-device-DEBUG: 05:04:12.021: Device reported finger status change: FP_FINGER_STATUS_NEEDED
155s (process:2350): libfprint-virtual_image-DEBUG: 05:04:12.021: image data: 0x31bcdc0
155s (process:2350): libfprint-device-DEBUG: 05:04:12.022: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.022: Image device reported finger status: on
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.022: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.022: Image device captured an image
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.022: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
155s (process:2350): libfprint-device-DEBUG: 05:04:12.022: Device reported finger status change: FP_FINGER_STATUS_PRESENT
155s (process:2350): libfprint-device-DEBUG: 05:04:12.022: Device reported finger status change: FP_FINGER_STATUS_NONE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.022: Image device reported finger status: off
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.022: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.022: Deactivating image device
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.022: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.022: Image device deactivation completed
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.022: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
155s (process:2350): libfprint-image-DEBUG: 05:04:12.044: Minutiae scan completed in 0.022774 secs
155s (process:2350): libfprint-print-DEBUG: 05:04:12.051: score 10/40
155s (process:2350): libfprint-print-DEBUG: 05:04:12.057: score 10/40
155s (process:2350): libfprint-print-DEBUG: 05:04:12.063: score 10/40
155s (process:2350): libfprint-print-DEBUG: 05:04:12.070: score 10/40
155s (process:2350): libfprint-print-DEBUG: 05:04:12.076: score 10/40
155s (process:2350): libfprint-device-DEBUG: 05:04:12.076: Device reported verify result
155s (process:2350): libfprint-device-DEBUG: 05:04:12.076: Device reported verify completion
155s (process:2350): libfprint-device-DEBUG: 05:04:12.076: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
155s (process:2350): libfprint-device-DEBUG: 05:04:12.076: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
155s (process:2350): libfprint-device-DEBUG: 05:04:12.076: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.076: Activating image device
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.076: Image device activation completed
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
155s (process:2350): libfprint-device-DEBUG: 05:04:12.076: Device reported finger status change: FP_FINGER_STATUS_NEEDED
155s (process:2350): libfprint-virtual_image-DEBUG: 05:04:12.076: image data: 0x31cbdd0
155s (process:2350): libfprint-device-DEBUG: 05:04:12.076: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.076: Image device reported finger status: on
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.076: Image device captured an image
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
155s (process:2350): libfprint-device-DEBUG: 05:04:12.076: Device reported finger status change: FP_FINGER_STATUS_PRESENT
155s (process:2350): libfprint-device-DEBUG: 05:04:12.076: Device reported finger status change: FP_FINGER_STATUS_NONE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.076: Image device reported finger status: off
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.076: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
155s (process:2350): libfprint-image-DEBUG: 05:04:12.099: Minutiae scan completed in 0.022897 secs
155s (process:2350): libfprint-device-DEBUG: 05:04:12.099: Device reported enroll progress, reported 1 of 5 have been completed
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.099: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
155s (process:2350): libfprint-device-DEBUG: 05:04:12.099: Device reported finger status change: FP_FINGER_STATUS_NEEDED
155s (process:2350): libfprint-device-DEBUG: 05:04:12.099: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.099: Image device reported finger status: on
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.099: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
155s (process:2350): libfprint-virtual_image-DEBUG: 05:04:12.099: image data: 0x31cbdd0
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.099: Image device captured an image
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.099: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
155s (process:2350): libfprint-device-DEBUG: 05:04:12.099: Device reported finger status change: FP_FINGER_STATUS_PRESENT
155s (process:2350): libfprint-image-DEBUG: 05:04:12.122: Minutiae scan completed in 0.022920 secs
155s (process:2350): libfprint-device-DEBUG: 05:04:12.122: Device reported enroll progress, reported 2 of 5 have been completed
155s (process:2350): libfprint-device-DEBUG: 05:04:12.122: Device reported finger status change: FP_FINGER_STATUS_NONE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.122: Image device reported finger status: off
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.122: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.122: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
155s (process:2350): libfprint-device-DEBUG: 05:04:12.122: Device reported finger status change: FP_FINGER_STATUS_NEEDED
155s (process:2350): libfprint-virtual_image-DEBUG: 05:04:12.123: image data: 0x31cbdd0
155s (process:2350): libfprint-device-DEBUG: 05:04:12.123: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.123: Image device reported finger status: on
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.123: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.123: Image device captured an image
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.123: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
155s (process:2350): libfprint-device-DEBUG: 05:04:12.123: Device reported finger status change: FP_FINGER_STATUS_PRESENT
155s (process:2350): libfprint-device-DEBUG: 05:04:12.123: Device reported finger status change: FP_FINGER_STATUS_NONE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.123: Image device reported finger status: off
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.123: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
155s (process:2350): libfprint-image-DEBUG: 05:04:12.145: Minutiae scan completed in 0.022687 secs
155s (process:2350): libfprint-device-DEBUG: 05:04:12.145: Device reported enroll progress, reported 3 of 5 have been completed
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.145: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
155s (process:2350): libfprint-device-DEBUG: 05:04:12.145: Device reported finger status change: FP_FINGER_STATUS_NEEDED
155s (process:2350): libfprint-virtual_image-DEBUG: 05:04:12.146: image data: 0x31cbdd0
155s (process:2350): libfprint-device-DEBUG: 05:04:12.146: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.146: Image device reported finger status: on
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.146: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.146: Image device captured an image
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.146: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
155s (process:2350): libfprint-device-DEBUG: 05:04:12.146: Device reported finger status change: FP_FINGER_STATUS_PRESENT
155s (process:2350): libfprint-device-DEBUG: 05:04:12.146: Device reported finger status change: FP_FINGER_STATUS_NONE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.146: Image device reported finger status: off
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.146: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
155s (process:2350): libfprint-image-DEBUG: 05:04:12.168: Minutiae scan completed in 0.022824 secs
155s (process:2350): libfprint-device-DEBUG: 05:04:12.168: Device reported enroll progress, reported 4 of 5 have been completed
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.169: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
155s (process:2350): libfprint-device-DEBUG: 05:04:12.169: Device reported finger status change: FP_FINGER_STATUS_NEEDED
155s (process:2350): libfprint-virtual_image-DEBUG: 05:04:12.169: image data: 0x31cbdd0
155s (process:2350): libfprint-device-DEBUG: 05:04:12.169: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.169: Image device reported finger status: on
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.169: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.169: Image device captured an image
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.169: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
155s (process:2350): libfprint-device-DEBUG: 05:04:12.169: Device reported finger status change: FP_FINGER_STATUS_PRESENT
155s (process:2350): libfprint-device-DEBUG: 05:04:12.169: Device reported finger status change: FP_FINGER_STATUS_NONE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.169: Image device reported finger status: off
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.169: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
155s (process:2350): libfprint-image-DEBUG: 05:04:12.192: Minutiae scan completed in 0.022809 secs
155s (process:2350): libfprint-device-DEBUG: 05:04:12.192: Device reported enroll progress, reported 5 of 5 have been completed
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.192: Deactivating image device
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.192: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.192: Image device deactivation completed
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.192: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
155s (process:2350): libfprint-device-DEBUG: 05:04:12.192: Device reported enroll completion
155s (process:2350): libfprint-device-DEBUG: 05:04:12.192: Print for finger FP_FINGER_LEFT_THUMB enrolled
155s (process:2350): libfprint-device-DEBUG: 05:04:12.192: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
155s (process:2350): libfprint-device-DEBUG: 05:04:12.192: Updated temperature model after 0.12 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
155s (process:2350): libfprint-device-DEBUG: 05:04:12.192: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.192: Activating image device
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.192: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.192: Image device activation completed
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.192: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.192: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
155s (process:2350): libfprint-device-DEBUG: 05:04:12.192: Device reported finger status change: FP_FINGER_STATUS_NEEDED
155s (process:2350): libfprint-virtual_image-DEBUG: 05:04:12.192: image data: 0x31bbe60
155s (process:2350): libfprint-device-DEBUG: 05:04:12.192: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.192: Image device reported finger status: on
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.192: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.192: Image device captured an image
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.192: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
155s (process:2350): libfprint-device-DEBUG: 05:04:12.195: Device reported finger status change: FP_FINGER_STATUS_PRESENT
155s (process:2350): libfprint-device-DEBUG: 05:04:12.195: Device reported finger status change: FP_FINGER_STATUS_NONE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.195: Image device reported finger status: off
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.195: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.195: Deactivating image device
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.195: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.195: Image device deactivation completed
155s (process:2350): libfprint-image_device-DEBUG: 05:04:12.195: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
155s (process:2350): libfprint-image-DEBUG: 05:04:12.218: Minutiae scan completed in 0.025534 secs
156s (process:2350): libfprint-print-DEBUG: 05:04:13.331: score 1093/40
156s (process:2350): libfprint-device-DEBUG: 05:04:13.331: Device reported verify result
156s (process:2350): libfprint-device-DEBUG: 05:04:13.331: Device reported verify completion
156s (process:2350): libfprint-device-DEBUG: 05:04:13.331: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
156s (process:2350): libfprint-device-DEBUG: 05:04:13.331: Updated temperature model after 1.14 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
156s (process:2350): libfprint-device-DEBUG: 05:04:13.331: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.331: Activating image device
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.331: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.331: Image device activation completed
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.331: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.331: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
156s (process:2350): libfprint-device-DEBUG: 05:04:13.331: Device reported finger status change: FP_FINGER_STATUS_NEEDED
156s (process:2350): libfprint-virtual_image-DEBUG: 05:04:13.332: image data: 0x31bcdc0
156s (process:2350): libfprint-device-DEBUG: 05:04:13.332: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.332: Image device reported finger status: on
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.332: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.332: Image device captured an image
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.332: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
156s (process:2350): libfprint-device-DEBUG: 05:04:13.335: Device reported finger status change: FP_FINGER_STATUS_PRESENT
156s (process:2350): libfprint-device-DEBUG: 05:04:13.335: Device reported finger status change: FP_FINGER_STATUS_NONE
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.335: Image device reported finger status: off
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.335: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.335: Deactivating image device
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.335: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.335: Image device deactivation completed
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.335: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
156s (process:2350): libfprint-image-DEBUG: 05:04:13.354: Minutiae scan completed in 0.022637 secs
156s (process:2350): libfprint-print-DEBUG: 05:04:13.361: score 10/40
156s (process:2350): libfprint-print-DEBUG: 05:04:13.367: score 10/40
156s (process:2350): libfprint-print-DEBUG: 05:04:13.373: score 10/40
156s (process:2350): libfprint-print-DEBUG: 05:04:13.379: score 10/40
156s (process:2350): libfprint-print-DEBUG: 05:04:13.385: score 10/40
156s (process:2350): libfprint-print-DEBUG: 05:04:13.609: score 855/40
156s (process:2350): libfprint-device-DEBUG: 05:04:13.609: Device reported verify result
156s (process:2350): libfprint-device-DEBUG: 05:04:13.609: Device reported verify completion
156s (process:2350): libfprint-device-DEBUG: 05:04:13.609: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
156s (process:2350): libfprint-device-DEBUG: 05:04:13.609: Updated temperature model after 0.28 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
156s (process:2350): libfprint-device-DEBUG: 05:04:13.609: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.609: Activating image device
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.609: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.609: Image device activation completed
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.609: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.609: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
156s (process:2350): libfprint-device-DEBUG: 05:04:13.609: Device reported finger status change: FP_FINGER_STATUS_NEEDED
156s (process:2350): libfprint-device-DEBUG: 05:04:13.609: Device reported verify result
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.609: Deactivating image device
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.609: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.609: Image device deactivation completed
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.609: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
156s (process:2350): libfprint-device-DEBUG: 05:04:13.609: Device reported verify completion
156s (process:2350): libfprint-device-DEBUG: 05:04:13.609: Device reported finger status change: FP_FINGER_STATUS_NONE
156s (process:2350): libfprint-device-DEBUG: 05:04:13.610: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
156s (process:2350): libfprint-device-DEBUG: 05:04:13.610: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
156s (process:2350): libfprint-device-DEBUG: 05:04:13.610: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.610: Activating image device
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.610: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.610: Image device activation completed
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.610: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.610: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
156s (process:2350): libfprint-device-DEBUG: 05:04:13.610: Device reported finger status change: FP_FINGER_STATUS_NEEDED
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.610: Deactivating image device
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.610: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.610: Image device deactivation completed
156s (process:2350): libfprint-image_device-DEBUG: 05:04:13.610: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
156s (process:2350): libfprint-device-DEBUG: 05:04:13.610: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_VERIFY
156s (process:2350): libfprint-device-DEBUG: 05:04:13.610: Device reported verify completion
156s (process:2350): libfprint-device-DEBUG: 05:04:13.610: Device reported finger status change: FP_FINGER_STATUS_NONE
156s (process:2350): libfprint-device-DEBUG: 05:04:13.610: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
156s (process:2350): libfprint-device-DEBUG: 05:04:13.610: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
156s (process:2350): libfprint-virtual_image-DEBUG: 05:04:13.610: 34685218: ../libfprint/drivers/virtual-image.c:244
157s (process:2350): libfprint-image_device-DEBUG: 05:04:13.710: Image device close completed
157s (process:2350): libfprint-device-DEBUG: 05:04:13.710: Device reported close completion
157s (process:2350): libfprint-device-DEBUG: 05:04:13.710: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
157s (process:2350): libfprint-device-DEBUG: 05:04:13.710: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
157s Print was processed, continuing
157s Print was processed, continuing
157s Print was processed, continuing
157s Print was processed, continuing
157s Print was processed, continuing
157s Enroll done
157s Print was processed, continuing
157s Print was processed, continuing
157s Print was processed, continuing
157s Print was processed, continuing
157s Print was processed, continuing
157s Enroll done
157s fp - device - error - quark: An unspecified error occurred! (0)
157s ok
157s test_features (__main__.VirtualImage.test_features) ... (process:2350): libfprint-virtual_image-DEBUG: 05:04:13.710: 34785607: ../libfprint/drivers/virtual-image.c:216
157s (process:2350): libfprint-virtual_device_connection-DEBUG: 05:04:13.710: 34785619: ../libfprint/drivers/virtual-device-listener.c:153
157s (process:2350): libfprint-image_device-DEBUG: 05:04:13.810: Image device open completed
157s (process:2350): libfprint-device-DEBUG: 05:04:13.810: Device reported open completion
157s (process:2350): libfprint-device-DEBUG: 05:04:13.810: Completing action FPI_DEVICE_ACTION_OPEN in idle!
157s (process:2350): libfprint-device-DEBUG: 05:04:13.810: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
157s (process:2350): libfprint-virtual_image-DEBUG: 05:04:13.810: 34885866: ../libfprint/drivers/virtual-image.c:244
157s (process:2350): libfprint-image_device-DEBUG: 05:04:13.910: Image device close completed
157s (process:2350): libfprint-device-DEBUG: 05:04:13.910: Device reported close completion
157s (process:2350): libfprint-device-DEBUG: 05:04:13.910: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
157s (process:2350): libfprint-device-DEBUG: 05:04:13.910: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
157s ok
157s test_identify (__main__.VirtualImage.test_identify) ... (process:2350): libfprint-virtual_image-DEBUG: 05:04:13.911: 34986059: ../libfprint/drivers/virtual-image.c:216
157s (process:2350): libfprint-virtual_device_connection-DEBUG: 05:04:13.911: 34986069: ../libfprint/drivers/virtual-device-listener.c:153
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.011: Image device open completed
157s (process:2350): libfprint-device-DEBUG: 05:04:14.011: Device reported open completion
157s (process:2350): libfprint-device-DEBUG: 05:04:14.011: Completing action FPI_DEVICE_ACTION_OPEN in idle!
157s (process:2350): libfprint-device-DEBUG: 05:04:14.011: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
157s (process:2350): libfprint-device-DEBUG: 05:04:14.011: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.011: Activating image device
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.011: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.011: Image device activation completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.011: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.011: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
157s (process:2350): libfprint-device-DEBUG: 05:04:14.011: Device reported finger status change: FP_FINGER_STATUS_NEEDED
157s (process:2350): libfprint-virtual_device_connection-DEBUG: 05:04:14.011: Got a new connection!
157s (process:2350): libfprint-virtual_image-DEBUG: 05:04:14.011: image data: 0x31bbe60
157s (process:2350): libfprint-device-DEBUG: 05:04:14.011: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.011: Image device reported finger status: on
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.011: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.011: Image device captured an image
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.015: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
157s (process:2350): libfprint-device-DEBUG: 05:04:14.015: Device reported finger status change: FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-device-DEBUG: 05:04:14.015: Device reported finger status change: FP_FINGER_STATUS_NONE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.015: Image device reported finger status: off
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.015: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image-DEBUG: 05:04:14.037: Minutiae scan completed in 0.025333 secs
157s (process:2350): libfprint-device-DEBUG: 05:04:14.037: Device reported enroll progress, reported 1 of 5 have been completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.037: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
157s (process:2350): libfprint-device-DEBUG: 05:04:14.037: Device reported finger status change: FP_FINGER_STATUS_NEEDED
157s (process:2350): libfprint-device-DEBUG: 05:04:14.037: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.037: Image device reported finger status: on
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.037: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
157s (process:2350): libfprint-virtual_image-DEBUG: 05:04:14.037: image data: 0x31bbe60
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.037: Image device captured an image
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.037: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
157s (process:2350): libfprint-device-DEBUG: 05:04:14.037: Device reported finger status change: FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-image-DEBUG: 05:04:14.063: Minutiae scan completed in 0.025534 secs
157s (process:2350): libfprint-device-DEBUG: 05:04:14.063: Device reported enroll progress, reported 2 of 5 have been completed
157s (process:2350): libfprint-device-DEBUG: 05:04:14.063: Device reported finger status change: FP_FINGER_STATUS_NONE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.063: Image device reported finger status: off
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.063: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.063: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
157s (process:2350): libfprint-device-DEBUG: 05:04:14.063: Device reported finger status change: FP_FINGER_STATUS_NEEDED
157s (process:2350): libfprint-virtual_image-DEBUG: 05:04:14.063: image data: 0x31bbe60
157s (process:2350): libfprint-device-DEBUG: 05:04:14.063: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.063: Image device reported finger status: on
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.063: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.063: Image device captured an image
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.063: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
157s (process:2350): libfprint-device-DEBUG: 05:04:14.063: Device reported finger status change: FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-device-DEBUG: 05:04:14.063: Device reported finger status change: FP_FINGER_STATUS_NONE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.063: Image device reported finger status: off
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.063: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image-DEBUG: 05:04:14.089: Minutiae scan completed in 0.025610 secs
157s (process:2350): libfprint-device-DEBUG: 05:04:14.089: Device reported enroll progress, reported 3 of 5 have been completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.089: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
157s (process:2350): libfprint-device-DEBUG: 05:04:14.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED
157s (process:2350): libfprint-virtual_image-DEBUG: 05:04:14.089: image data: 0x31bbe60
157s (process:2350): libfprint-device-DEBUG: 05:04:14.089: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.089: Image device reported finger status: on
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.089: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.089: Image device captured an image
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.089: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
157s (process:2350): libfprint-device-DEBUG: 05:04:14.089: Device reported finger status change: FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-device-DEBUG: 05:04:14.089: Device reported finger status change: FP_FINGER_STATUS_NONE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.089: Image device reported finger status: off
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.089: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image-DEBUG: 05:04:14.114: Minutiae scan completed in 0.025206 secs
157s (process:2350): libfprint-device-DEBUG: 05:04:14.114: Device reported enroll progress, reported 4 of 5 have been completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
157s (process:2350): libfprint-device-DEBUG: 05:04:14.114: Device reported finger status change: FP_FINGER_STATUS_NEEDED
157s (process:2350): libfprint-virtual_image-DEBUG: 05:04:14.114: image data: 0x31bbe60
157s (process:2350): libfprint-device-DEBUG: 05:04:14.114: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.114: Image device reported finger status: on
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.114: Image device captured an image
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
157s (process:2350): libfprint-device-DEBUG: 05:04:14.114: Device reported finger status change: FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-device-DEBUG: 05:04:14.114: Device reported finger status change: FP_FINGER_STATUS_NONE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.114: Image device reported finger status: off
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.114: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image-DEBUG: 05:04:14.140: Minutiae scan completed in 0.025503 secs
157s (process:2350): libfprint-device-DEBUG: 05:04:14.140: Device reported enroll progress, reported 5 of 5 have been completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Deactivating image device
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Image device deactivation completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
157s (process:2350): libfprint-device-DEBUG: 05:04:14.140: Device reported enroll completion
157s (process:2350): libfprint-device-DEBUG: 05:04:14.140: Print for finger FP_FINGER_LEFT_THUMB enrolled
157s (process:2350): libfprint-device-DEBUG: 05:04:14.140: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
157s (process:2350): libfprint-device-DEBUG: 05:04:14.140: Updated temperature model after 0.13 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
157s (process:2350): libfprint-device-DEBUG: 05:04:14.140: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Activating image device
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Image device activation completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
157s (process:2350): libfprint-device-DEBUG: 05:04:14.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED
157s (process:2350): libfprint-virtual_image-DEBUG: 05:04:14.140: image data: 0x31bcdc0
157s (process:2350): libfprint-device-DEBUG: 05:04:14.140: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Image device reported finger status: on
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Image device captured an image
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
157s (process:2350): libfprint-device-DEBUG: 05:04:14.140: Device reported finger status change: FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-device-DEBUG: 05:04:14.140: Device reported finger status change: FP_FINGER_STATUS_NONE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Image device reported finger status: off
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.140: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image-DEBUG: 05:04:14.163: Minutiae scan completed in 0.022404 secs
157s (process:2350): libfprint-device-DEBUG: 05:04:14.163: Device reported enroll progress, reported 1 of 5 have been completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.163: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
157s (process:2350): libfprint-device-DEBUG: 05:04:14.163: Device reported finger status change: FP_FINGER_STATUS_NEEDED
157s (process:2350): libfprint-device-DEBUG: 05:04:14.163: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.163: Image device reported finger status: on
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.163: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
157s (process:2350): libfprint-virtual_image-DEBUG: 05:04:14.163: image data: 0x31bcdc0
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.163: Image device captured an image
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.163: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
157s (process:2350): libfprint-device-DEBUG: 05:04:14.163: Device reported finger status change: FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-image-DEBUG: 05:04:14.186: Minutiae scan completed in 0.022403 secs
157s (process:2350): libfprint-device-DEBUG: 05:04:14.186: Device reported enroll progress, reported 2 of 5 have been completed
157s (process:2350): libfprint-device-DEBUG: 05:04:14.186: Device reported finger status change: FP_FINGER_STATUS_NONE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.186: Image device reported finger status: off
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.186: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.186: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
157s (process:2350): libfprint-device-DEBUG: 05:04:14.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED
157s (process:2350): libfprint-virtual_image-DEBUG: 05:04:14.186: image data: 0x31bd730
157s (process:2350): libfprint-device-DEBUG: 05:04:14.186: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.186: Image device reported finger status: on
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.186: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.186: Image device captured an image
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.186: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
157s (process:2350): libfprint-device-DEBUG: 05:04:14.186: Device reported finger status change: FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-device-DEBUG: 05:04:14.186: Device reported finger status change: FP_FINGER_STATUS_NONE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.186: Image device reported finger status: off
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.186: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image-DEBUG: 05:04:14.209: Minutiae scan completed in 0.022621 secs
157s (process:2350): libfprint-device-DEBUG: 05:04:14.209: Device reported enroll progress, reported 3 of 5 have been completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.209: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
157s (process:2350): libfprint-device-DEBUG: 05:04:14.209: Device reported finger status change: FP_FINGER_STATUS_NEEDED
157s (process:2350): libfprint-virtual_image-DEBUG: 05:04:14.209: image data: 0x31be0a0
157s (process:2350): libfprint-device-DEBUG: 05:04:14.209: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.209: Image device reported finger status: on
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.209: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.209: Image device captured an image
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.209: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
157s (process:2350): libfprint-device-DEBUG: 05:04:14.209: Device reported finger status change: FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-device-DEBUG: 05:04:14.209: Device reported finger status change: FP_FINGER_STATUS_NONE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.209: Image device reported finger status: off
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.209: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image-DEBUG: 05:04:14.231: Minutiae scan completed in 0.022491 secs
157s (process:2350): libfprint-device-DEBUG: 05:04:14.231: Device reported enroll progress, reported 4 of 5 have been completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.231: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
157s (process:2350): libfprint-device-DEBUG: 05:04:14.231: Device reported finger status change: FP_FINGER_STATUS_NEEDED
157s (process:2350): libfprint-virtual_image-DEBUG: 05:04:14.231: image data: 0x31bea10
157s (process:2350): libfprint-device-DEBUG: 05:04:14.232: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.232: Image device reported finger status: on
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.232: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.232: Image device captured an image
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.235: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
157s (process:2350): libfprint-device-DEBUG: 05:04:14.235: Device reported finger status change: FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-device-DEBUG: 05:04:14.235: Device reported finger status change: FP_FINGER_STATUS_NONE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.235: Image device reported finger status: off
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.235: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image-DEBUG: 05:04:14.254: Minutiae scan completed in 0.022730 secs
157s (process:2350): libfprint-device-DEBUG: 05:04:14.254: Device reported enroll progress, reported 5 of 5 have been completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.254: Deactivating image device
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.254: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.254: Image device deactivation completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.254: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
157s (process:2350): libfprint-device-DEBUG: 05:04:14.254: Device reported enroll completion
157s (process:2350): libfprint-device-DEBUG: 05:04:14.254: Print for finger FP_FINGER_LEFT_THUMB enrolled
157s (process:2350): libfprint-device-DEBUG: 05:04:14.254: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
157s (process:2350): libfprint-device-DEBUG: 05:04:14.254: Updated temperature model after 0.11 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
157s (process:2350): libfprint-device-DEBUG: 05:04:14.255: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Activating image device
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Image device activation completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
157s (process:2350): libfprint-device-DEBUG: 05:04:14.255: Device reported finger status change: FP_FINGER_STATUS_NEEDED
157s (process:2350): libfprint-virtual_image-DEBUG: 05:04:14.255: image data: 0x31dca60
157s (process:2350): libfprint-device-DEBUG: 05:04:14.255: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Image device reported finger status: on
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Image device captured an image
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
157s (process:2350): libfprint-device-DEBUG: 05:04:14.255: Device reported finger status change: FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-device-DEBUG: 05:04:14.255: Device reported finger status change: FP_FINGER_STATUS_NONE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Image device reported finger status: off
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Deactivating image device
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Image device deactivation completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.255: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
157s (process:2350): libfprint-image-DEBUG: 05:04:14.278: Minutiae scan completed in 0.023293 secs
157s (process:2350): libfprint-print-DEBUG: 05:04:14.285: score 10/40
157s (process:2350): libfprint-print-DEBUG: 05:04:14.291: score 10/40
157s (process:2350): libfprint-print-DEBUG: 05:04:14.297: score 10/40
157s (process:2350): libfprint-print-DEBUG: 05:04:14.303: score 10/40
157s (process:2350): libfprint-print-DEBUG: 05:04:14.309: score 10/40
157s (process:2350): libfprint-print-DEBUG: 05:04:14.544: score 855/40
157s (process:2350): libfprint-device-DEBUG: 05:04:14.544: Device reported identify result
157s (process:2350): libfprint-device-DEBUG: 05:04:14.544: Device reported identify completion
157s (process:2350): libfprint-device-DEBUG: 05:04:14.544: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
157s (process:2350): libfprint-device-DEBUG: 05:04:14.544: Updated temperature model after 0.29 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
157s (process:2350): libfprint-device-DEBUG: 05:04:14.544: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.544: Activating image device
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.544: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.544: Image device activation completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.544: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.544: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
157s (process:2350): libfprint-device-DEBUG: 05:04:14.544: Device reported finger status change: FP_FINGER_STATUS_NEEDED
157s (process:2350): libfprint-virtual_image-DEBUG: 05:04:14.544: image data: 0x31ce990
157s (process:2350): libfprint-device-DEBUG: 05:04:14.544: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.544: Image device reported finger status: on
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.544: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.544: Image device captured an image
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.544: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
157s (process:2350): libfprint-device-DEBUG: 05:04:14.545: Device reported finger status change: FP_FINGER_STATUS_PRESENT
157s (process:2350): libfprint-device-DEBUG: 05:04:14.545: Device reported finger status change: FP_FINGER_STATUS_NONE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.545: Image device reported finger status: off
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.545: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.545: Deactivating image device
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.545: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.545: Image device deactivation completed
157s (process:2350): libfprint-image_device-DEBUG: 05:04:14.545: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
157s (process:2350): libfprint-image-DEBUG: 05:04:14.570: Minutiae scan completed in 0.025352 secs
158s Executing: libfprint-2/virtual-image.test
159s (process:2350): libfprint-print-DEBUG: 05:04:15.694: score 1093/40
159s (process:2350): libfprint-device-DEBUG: 05:04:15.694: Device reported identify result
159s (process:2350): libfprint-device-DEBUG: 05:04:15.694: Device reported identify completion
159s (process:2350): libfprint-device-DEBUG: 05:04:15.694: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
159s (process:2350): libfprint-device-DEBUG: 05:04:15.694: Updated temperature model after 1.15 seconds, ratio 0.28 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
159s (process:2350): libfprint-device-DEBUG: 05:04:15.694: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.694: Activating image device
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.694: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.694: Image device activation completed
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.694: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.694: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
159s (process:2350): libfprint-device-DEBUG: 05:04:15.694: Device reported finger status change: FP_FINGER_STATUS_NEEDED
159s (process:2350): libfprint-device-DEBUG: 05:04:15.694: Device reported identify result
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.694: Deactivating image device
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.694: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.694: Image device deactivation completed
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.694: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
159s (process:2350): libfprint-device-DEBUG: 05:04:15.694: Device reported identify completion
159s (process:2350): libfprint-device-DEBUG: 05:04:15.694: Device reported finger status change: FP_FINGER_STATUS_NONE
159s (process:2350): libfprint-device-DEBUG: 05:04:15.694: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
159s (process:2350): libfprint-device-DEBUG: 05:04:15.694: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
159s (process:2350): libfprint-device-DEBUG: 05:04:15.695: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.695: Activating image device
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.695: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.695: Image device activation completed
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.695: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.695: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
159s (process:2350): libfprint-device-DEBUG: 05:04:15.695: Device reported finger status change: FP_FINGER_STATUS_NEEDED
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.695: Deactivating image device
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.695: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.695: Image device deactivation completed
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.695: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
159s (process:2350): libfprint-device-DEBUG: 05:04:15.695: Device reported generic error (An unspecified error occurred!) during action; action was: FPI_DEVICE_ACTION_IDENTIFY
159s (process:2350): libfprint-device-DEBUG: 05:04:15.695: Device reported identify completion
159s (process:2350): libfprint-device-DEBUG: 05:04:15.695: Device reported finger status change: FP_FINGER_STATUS_NONE
159s (process:2350): libfprint-device-DEBUG: 05:04:15.695: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
159s (process:2350): libfprint-device-DEBUG: 05:04:15.695: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
159s (process:2350): libfprint-virtual_image-DEBUG: 05:04:15.695: 36770141: ../libfprint/drivers/virtual-image.c:244
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.795: Image device close completed
159s (process:2350): libfprint-device-DEBUG: 05:04:15.795: Device reported close completion
159s (process:2350): libfprint-device-DEBUG: 05:04:15.795: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
159s (process:2350): libfprint-device-DEBUG: 05:04:15.795: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
159s Print was processed, continuing
159s Print was processed, continuing
159s Print was processed, continuing
159s Print was processed, continuing
159s Print was processed, continuing
159s Enroll done
159s Print was processed, continuing
159s Print was processed, continuing
159s Print was processed, continuing
159s Print was processed, continuing
159s Print was processed, continuing
159s Enroll done
159s Identify finished
159s Identify finished
159s Identify finished
159s fp - device - retry - quark: The swipe was too short, please try again. (1)
159s Identify finished
159s fp - device - error - quark: An unspecified error occurred! (0)
159s ok
159s test_verify_serialized (__main__.VirtualImage.test_verify_serialized) ... (process:2350): libfprint-virtual_image-DEBUG: 05:04:15.795: 36870623: ../libfprint/drivers/virtual-image.c:216
159s (process:2350): libfprint-virtual_device_connection-DEBUG: 05:04:15.795: 36870636: ../libfprint/drivers/virtual-device-listener.c:153
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.895: Image device open completed
159s (process:2350): libfprint-device-DEBUG: 05:04:15.895: Device reported open completion
159s (process:2350): libfprint-device-DEBUG: 05:04:15.895: Completing action FPI_DEVICE_ACTION_OPEN in idle!
159s (process:2350): libfprint-device-DEBUG: 05:04:15.895: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
159s (process:2350): libfprint-device-DEBUG: 05:04:15.896: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.896: Activating image device
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.896: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.896: Image device activation completed
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.896: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.896: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
159s (process:2350): libfprint-device-DEBUG: 05:04:15.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED
159s (process:2350): libfprint-virtual_device_connection-DEBUG: 05:04:15.896: Got a new connection!
159s (process:2350): libfprint-virtual_image-DEBUG: 05:04:15.896: image data: 0x31ce970
159s (process:2350): libfprint-device-DEBUG: 05:04:15.896: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.896: Image device reported finger status: on
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.896: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.896: Image device captured an image
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.896: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
159s (process:2350): libfprint-device-DEBUG: 05:04:15.896: Device reported finger status change: FP_FINGER_STATUS_PRESENT
159s (process:2350): libfprint-device-DEBUG: 05:04:15.896: Device reported finger status change: FP_FINGER_STATUS_NONE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.896: Image device reported finger status: off
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.896: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
159s (process:2350): libfprint-image-DEBUG: 05:04:15.922: Minutiae scan completed in 0.025946 secs
159s (process:2350): libfprint-device-DEBUG: 05:04:15.922: Device reported enroll progress, reported 1 of 5 have been completed
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.922: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
159s (process:2350): libfprint-device-DEBUG: 05:04:15.922: Device reported finger status change: FP_FINGER_STATUS_NEEDED
159s (process:2350): libfprint-device-DEBUG: 05:04:15.922: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.922: Image device reported finger status: on
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.922: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
159s (process:2350): libfprint-virtual_image-DEBUG: 05:04:15.922: image data: 0x31ce970
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.923: Image device captured an image
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.923: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
159s (process:2350): libfprint-device-DEBUG: 05:04:15.923: Device reported finger status change: FP_FINGER_STATUS_PRESENT
159s (process:2350): libfprint-image-DEBUG: 05:04:15.948: Minutiae scan completed in 0.025795 secs
159s (process:2350): libfprint-device-DEBUG: 05:04:15.949: Device reported enroll progress, reported 2 of 5 have been completed
159s (process:2350): libfprint-device-DEBUG: 05:04:15.949: Device reported finger status change: FP_FINGER_STATUS_NONE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.949: Image device reported finger status: off
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.949: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.949: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
159s (process:2350): libfprint-device-DEBUG: 05:04:15.949: Device reported finger status change: FP_FINGER_STATUS_NEEDED
159s (process:2350): libfprint-virtual_image-DEBUG: 05:04:15.949: image data: 0x31ce970
159s (process:2350): libfprint-device-DEBUG: 05:04:15.949: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.949: Image device reported finger status: on
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.949: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.949: Image device captured an image
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.949: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
159s (process:2350): libfprint-device-DEBUG: 05:04:15.949: Device reported finger status change: FP_FINGER_STATUS_PRESENT
159s (process:2350): libfprint-device-DEBUG: 05:04:15.949: Device reported finger status change: FP_FINGER_STATUS_NONE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.949: Image device reported finger status: off
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.949: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
159s (process:2350): libfprint-image-DEBUG: 05:04:15.974: Minutiae scan completed in 0.025540 secs
159s (process:2350): libfprint-device-DEBUG: 05:04:15.974: Device reported enroll progress, reported 3 of 5 have been completed
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.974: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
159s (process:2350): libfprint-device-DEBUG: 05:04:15.974: Device reported finger status change: FP_FINGER_STATUS_NEEDED
159s (process:2350): libfprint-virtual_image-DEBUG: 05:04:15.975: image data: 0x31ce970
159s (process:2350): libfprint-device-DEBUG: 05:04:15.975: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.975: Image device reported finger status: on
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.975: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.975: Image device captured an image
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.975: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
159s (process:2350): libfprint-device-DEBUG: 05:04:15.975: Device reported finger status change: FP_FINGER_STATUS_PRESENT
159s (process:2350): libfprint-device-DEBUG: 05:04:15.975: Device reported finger status change: FP_FINGER_STATUS_NONE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.975: Image device reported finger status: off
159s (process:2350): libfprint-image_device-DEBUG: 05:04:15.975: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
159s (process:2350): libfprint-image-DEBUG: 05:04:16.000: Minutiae scan completed in 0.025733 secs
159s (process:2350): libfprint-device-DEBUG: 05:04:16.000: Device reported enroll progress, reported 4 of 5 have been completed
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.000: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
159s (process:2350): libfprint-device-DEBUG: 05:04:16.001: Device reported finger status change: FP_FINGER_STATUS_NEEDED
159s (process:2350): libfprint-virtual_image-DEBUG: 05:04:16.001: image data: 0x31ce970
159s (process:2350): libfprint-device-DEBUG: 05:04:16.001: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.001: Image device reported finger status: on
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.001: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.001: Image device captured an image
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.001: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
159s (process:2350): libfprint-device-DEBUG: 05:04:16.001: Device reported finger status change: FP_FINGER_STATUS_PRESENT
159s (process:2350): libfprint-device-DEBUG: 05:04:16.001: Device reported finger status change: FP_FINGER_STATUS_NONE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.001: Image device reported finger status: off
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.001: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
159s (process:2350): libfprint-image-DEBUG: 05:04:16.026: Minutiae scan completed in 0.025766 secs
159s (process:2350): libfprint-device-DEBUG: 05:04:16.027: Device reported enroll progress, reported 5 of 5 have been completed
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Deactivating image device
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device deactivation completed
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
159s (process:2350): libfprint-device-DEBUG: 05:04:16.027: Device reported enroll completion
159s (process:2350): libfprint-device-DEBUG: 05:04:16.027: Print for finger FP_FINGER_LEFT_THUMB enrolled
159s (process:2350): libfprint-device-DEBUG: 05:04:16.027: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
159s (process:2350): libfprint-device-DEBUG: 05:04:16.027: Updated temperature model after 0.13 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
159s (process:2350): libfprint-device-DEBUG: 05:04:16.027: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Activating image device
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device activation completed
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
159s (process:2350): libfprint-device-DEBUG: 05:04:16.027: Device reported finger status change: FP_FINGER_STATUS_NEEDED
159s (process:2350): libfprint-virtual_image-DEBUG: 05:04:16.027: image data: 0x31ce970
159s (process:2350): libfprint-device-DEBUG: 05:04:16.027: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device reported finger status: on
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device captured an image
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
159s (process:2350): libfprint-device-DEBUG: 05:04:16.027: Device reported finger status change: FP_FINGER_STATUS_PRESENT
159s (process:2350): libfprint-device-DEBUG: 05:04:16.027: Device reported finger status change: FP_FINGER_STATUS_NONE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device reported finger status: off
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Deactivating image device
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device deactivation completed
159s (process:2350): libfprint-image_device-DEBUG: 05:04:16.027: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
159s (process:2350): libfprint-image-DEBUG: 05:04:16.053: Minutiae scan completed in 0.025563 secs
160s (process:2350): libfprint-print-DEBUG: 05:04:17.177: score 1093/40
160s (process:2350): libfprint-device-DEBUG: 05:04:17.177: Device reported verify result
160s (process:2350): libfprint-device-DEBUG: 05:04:17.177: Device reported verify completion
160s (process:2350): libfprint-device-DEBUG: 05:04:17.177: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
160s (process:2350): libfprint-device-DEBUG: 05:04:17.177: Updated temperature model after 1.15 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
160s (process:2350): libfprint-device-DEBUG: 05:04:17.177: Updated temperature model after 0.00 seconds, ratio 0.29 -> 0.29, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.177: Activating image device
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.177: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.177: Image device activation completed
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.177: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.177: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
160s (process:2350): libfprint-device-DEBUG: 05:04:17.177: Device reported finger status change: FP_FINGER_STATUS_NEEDED
160s (process:2350): libfprint-virtual_image-DEBUG: 05:04:17.178: image data: 0x31cf8d0
160s (process:2350): libfprint-device-DEBUG: 05:04:17.178: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.178: Image device reported finger status: on
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.178: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.178: Image device captured an image
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.178: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
160s (process:2350): libfprint-device-DEBUG: 05:04:17.178: Device reported finger status change: FP_FINGER_STATUS_PRESENT
160s (process:2350): libfprint-device-DEBUG: 05:04:17.178: Device reported finger status change: FP_FINGER_STATUS_NONE
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.178: Image device reported finger status: off
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.178: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.178: Deactivating image device
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.178: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.178: Image device deactivation completed
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.178: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
160s (process:2350): libfprint-image-DEBUG: 05:04:17.203: Minutiae scan completed in 0.025263 secs
160s (process:2350): libfprint-print-DEBUG: 05:04:17.210: score 10/40
160s (process:2350): libfprint-print-DEBUG: 05:04:17.216: score 10/40
160s (process:2350): libfprint-print-DEBUG: 05:04:17.222: score 10/40
160s (process:2350): libfprint-print-DEBUG: 05:04:17.229: score 10/40
160s (process:2350): libfprint-print-DEBUG: 05:04:17.235: score 10/40
160s (process:2350): libfprint-device-DEBUG: 05:04:17.235: Device reported verify result
160s (process:2350): libfprint-device-DEBUG: 05:04:17.235: Device reported verify completion
160s (process:2350): libfprint-device-DEBUG: 05:04:17.235: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
160s (process:2350): libfprint-device-DEBUG: 05:04:17.235: Updated temperature model after 0.06 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
160s (process:2350): libfprint-virtual_image-DEBUG: 05:04:17.235: 38310718: ../libfprint/drivers/virtual-image.c:244
160s (process:2350): libfprint-image_device-DEBUG: 05:04:17.335: Image device close completed
160s (process:2350): libfprint-device-DEBUG: 05:04:17.335: Device reported close completion
160s (process:2350): libfprint-device-DEBUG: 05:04:17.335: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
160s (process:2350): libfprint-device-DEBUG: 05:04:17.335: Updated temperature model after 0.10 seconds, ratio 0.29 -> 0.29, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
160s Print was processed, continuing
160s Print was processed, continuing
160s Print was processed, continuing
160s Print was processed, continuing
160s Print was processed, continuing
160s Enroll done
160s ok
160s 
160s ----------------------------------------------------------------------
160s Ran 5 tests in 6.898s
160s 
160s OK
160s PASS: libfprint-2/virtual-image.test
160s Running test: libfprint-2/fp-device.test
160s TAP version 14
160s # random seed: R02S13c7217a4f4e3bc969ce5990ab58d6f8
160s 1..17
160s # Start of device tests
160s # Start of async tests
160s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
160s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
160s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-GOSG22/virtual_image.socket
160s # libfprint-context-DEBUG: created
160s # libfprint-device-DEBUG: Device reported probe completion
160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
160s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:17.358: 38433293: ../libfprint/drivers/virtual-image.c:216
160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:04:17.358: 38433355: ../libfprint/drivers/virtual-device-listener.c:153
160s # libfprint-image_device-DEBUG: Image device open completed
160s # libfprint-device-DEBUG: Device reported open completion
160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
160s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:17.459: 38533939: ../libfprint/drivers/virtual-image.c:244
160s # libfprint-image_device-DEBUG: Image device close completed
160s # libfprint-device-DEBUG: Device reported close completion
160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
160s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
160s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
160s ok 1 /device/async/open
160s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
160s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
160s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
160s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-UB8112/virtual_image.socket
160s # libfprint-context-DEBUG: created
160s # libfprint-device-DEBUG: Device reported probe completion
160s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
160s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:17.560: 38635478: ../libfprint/drivers/virtual-image.c:216
160s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:04:17.560: 38635496: ../libfprint/drivers/virtual-device-listener.c:153
161s # libfprint-image_device-DEBUG: Image device open completed
161s # libfprint-device-DEBUG: Device reported open completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:17.660: 38735889: ../libfprint/drivers/virtual-image.c:244
161s # libfprint-image_device-DEBUG: Image device close completed
161s # libfprint-device-DEBUG: Device reported close completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
161s ok 2 /device/async/close
161s # End of async tests
161s # Start of sync tests
161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
161s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
161s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-ASK312/virtual_image.socket
161s # libfprint-context-DEBUG: created
161s # libfprint-device-DEBUG: Device reported probe completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:17.762: 38837370: ../libfprint/drivers/virtual-image.c:216
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:04:17.762: 38837397: ../libfprint/drivers/virtual-device-listener.c:153
161s # libfprint-image_device-DEBUG: Image device open completed
161s # libfprint-device-DEBUG: Device reported open completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:17.862: 38937860: ../libfprint/drivers/virtual-image.c:244
161s # libfprint-image_device-DEBUG: Image device close completed
161s # libfprint-device-DEBUG: Device reported close completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
161s ok 3 /device/sync/open
161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
161s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
161s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-3TTA22/virtual_image.socket
161s # libfprint-context-DEBUG: created
161s # libfprint-device-DEBUG: Device reported probe completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:17.964: 39039276: ../libfprint/drivers/virtual-image.c:216
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:04:17.964: 39039300: ../libfprint/drivers/virtual-device-listener.c:153
161s # libfprint-image_device-DEBUG: Image device open completed
161s # libfprint-device-DEBUG: Device reported open completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:18.064: 39139784: ../libfprint/drivers/virtual-image.c:244
161s # libfprint-image_device-DEBUG: Image device close completed
161s # libfprint-device-DEBUG: Device reported close completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
161s ok 4 /device/sync/close
161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
161s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
161s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-WNCG22/virtual_image.socket
161s # libfprint-context-DEBUG: created
161s # libfprint-device-DEBUG: Device reported probe completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:18.166: 39241352: ../libfprint/drivers/virtual-image.c:216
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:04:18.166: 39241380: ../libfprint/drivers/virtual-device-listener.c:153
161s # libfprint-image_device-DEBUG: Image device open completed
161s # libfprint-device-DEBUG: Device reported open completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:18.266: 39341856: ../libfprint/drivers/virtual-image.c:244
161s # libfprint-image_device-DEBUG: Image device close completed
161s # libfprint-device-DEBUG: Device reported close completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
161s ok 5 /device/sync/get_driver
161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
161s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
161s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-COLH22/virtual_image.socket
161s # libfprint-context-DEBUG: created
161s # libfprint-device-DEBUG: Device reported probe completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:18.368: 39443148: ../libfprint/drivers/virtual-image.c:216
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:04:18.368: 39443174: ../libfprint/drivers/virtual-device-listener.c:153
161s # libfprint-image_device-DEBUG: Image device open completed
161s # libfprint-device-DEBUG: Device reported open completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:18.468: 39543638: ../libfprint/drivers/virtual-image.c:244
161s # libfprint-image_device-DEBUG: Image device close completed
161s # libfprint-device-DEBUG: Device reported close completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
161s ok 6 /device/sync/get_device_id
161s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
161s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
161s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
161s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-ONF212/virtual_image.socket
161s # libfprint-context-DEBUG: created
161s # libfprint-device-DEBUG: Device reported probe completion
161s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
161s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:18.570: 39644962: ../libfprint/drivers/virtual-image.c:216
161s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:04:18.570: 39644989: ../libfprint/drivers/virtual-device-listener.c:153
162s # libfprint-image_device-DEBUG: Image device open completed
162s # libfprint-device-DEBUG: Device reported open completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:18.670: 39745396: ../libfprint/drivers/virtual-image.c:244
162s # libfprint-image_device-DEBUG: Image device close completed
162s # libfprint-device-DEBUG: Device reported close completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
162s ok 7 /device/sync/get_name
162s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
162s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
162s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
162s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-C6C312/virtual_image.socket
162s # libfprint-context-DEBUG: created
162s # libfprint-device-DEBUG: Device reported probe completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:18.771: 39846649: ../libfprint/drivers/virtual-image.c:216
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:04:18.771: 39846668: ../libfprint/drivers/virtual-device-listener.c:153
162s # libfprint-image_device-DEBUG: Image device open completed
162s # libfprint-device-DEBUG: Device reported open completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:18.872: 39947179: ../libfprint/drivers/virtual-image.c:244
162s # libfprint-image_device-DEBUG: Image device close completed
162s # libfprint-device-DEBUG: Device reported close completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
162s ok 8 /device/sync/get_scan_type
162s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
162s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
162s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
162s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-3H8912/virtual_image.socket
162s # libfprint-context-DEBUG: created
162s # libfprint-device-DEBUG: Device reported probe completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:18.973: 40048378: ../libfprint/drivers/virtual-image.c:216
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:04:18.973: 40048392: ../libfprint/drivers/virtual-device-listener.c:153
162s # libfprint-image_device-DEBUG: Image device open completed
162s # libfprint-device-DEBUG: Device reported open completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:19.073: 40148822: ../libfprint/drivers/virtual-image.c:244
162s # libfprint-image_device-DEBUG: Image device close completed
162s # libfprint-device-DEBUG: Device reported close completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
162s ok 9 /device/sync/get_finger_status
162s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
162s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
162s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
162s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-UGGG22/virtual_image.socket
162s # libfprint-context-DEBUG: created
162s # libfprint-device-DEBUG: Device reported probe completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:04:19.175: 40250117: ../libfprint/drivers/virtual-image.c:216
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:04:19.175: 40250133: ../libfprint/drivers/virtual-device-listener.c:153
162s # libfprint-image_device-DEBUG: Image device open completed
162s # libfprint-device-DEBUG: Device reported open completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:53.603: 40351725: ../libfprint/drivers/virtual-image.c:244
162s # libfprint-image_device-DEBUG: Image device close completed
162s # libfprint-device-DEBUG: Device reported close completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
162s ok 10 /device/sync/get_nr_enroll_stages
162s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
162s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
162s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
162s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-LX4412/virtual_image.socket
162s # libfprint-context-DEBUG: created
162s # libfprint-device-DEBUG: Device reported probe completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:53.703: 40452645: ../libfprint/drivers/virtual-image.c:216
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:02:53.704: 40452671: ../libfprint/drivers/virtual-device-listener.c:153
162s # libfprint-image_device-DEBUG: Image device open completed
162s # libfprint-device-DEBUG: Device reported open completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:53.804: 40553001: ../libfprint/drivers/virtual-image.c:244
162s # libfprint-image_device-DEBUG: Image device close completed
162s # libfprint-device-DEBUG: Device reported close completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
162s ok 11 /device/sync/supports_identify
162s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
162s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
162s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
162s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-I59512/virtual_image.socket
162s # libfprint-context-DEBUG: created
162s # libfprint-device-DEBUG: Device reported probe completion
162s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
162s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:53.912: 40661013: ../libfprint/drivers/virtual-image.c:216
162s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:02:53.912: 40661071: ../libfprint/drivers/virtual-device-listener.c:153
163s # libfprint-image_device-DEBUG: Image device open completed
163s # libfprint-device-DEBUG: Device reported open completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:54.012: 40761546: ../libfprint/drivers/virtual-image.c:244
163s # libfprint-image_device-DEBUG: Image device close completed
163s # libfprint-device-DEBUG: Device reported close completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
163s ok 12 /device/sync/supports_capture
163s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
163s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
163s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
163s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-6N5B22/virtual_image.socket
163s # libfprint-context-DEBUG: created
163s # libfprint-device-DEBUG: Device reported probe completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:54.114: 40862988: ../libfprint/drivers/virtual-image.c:216
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:02:54.114: 40863002: ../libfprint/drivers/virtual-device-listener.c:153
163s # libfprint-image_device-DEBUG: Image device open completed
163s # libfprint-device-DEBUG: Device reported open completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:54.215: 40963677: ../libfprint/drivers/virtual-image.c:244
163s Executing: libfprint-2/fp-device.test
163s # libfprint-image_device-DEBUG: Image device close completed
163s # libfprint-device-DEBUG: Device reported close completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
163s ok 13 /device/sync/has_storage
163s # Start of open tests
163s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
163s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
163s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
163s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-GGPI22/virtual_image.socket
163s # libfprint-context-DEBUG: created
163s # libfprint-device-DEBUG: Device reported probe completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:54.316: 41064883: ../libfprint/drivers/virtual-image.c:216
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:02:54.316: 41064913: ../libfprint/drivers/virtual-device-listener.c:153
163s # libfprint-image_device-DEBUG: Image device open completed
163s # libfprint-device-DEBUG: Device reported open completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:54.416: 41165313: ../libfprint/drivers/virtual-image.c:244
163s # libfprint-image_device-DEBUG: Image device close completed
163s # libfprint-device-DEBUG: Device reported close completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
163s ok 14 /device/sync/open/notify
163s # End of open tests
163s # Start of close tests
163s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
163s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
163s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
163s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-88DK22/virtual_image.socket
163s # libfprint-context-DEBUG: created
163s # libfprint-device-DEBUG: Device reported probe completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:54.517: 41266521: ../libfprint/drivers/virtual-image.c:216
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:02:54.517: 41266537: ../libfprint/drivers/virtual-device-listener.c:153
163s # libfprint-image_device-DEBUG: Image device open completed
163s # libfprint-device-DEBUG: Device reported open completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:54.618: 41367000: ../libfprint/drivers/virtual-image.c:244
163s # libfprint-image_device-DEBUG: Image device close completed
163s # libfprint-device-DEBUG: Device reported close completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
163s ok 15 /device/sync/close/notify
163s # End of close tests
163s # Start of identify tests
163s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
163s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
163s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
163s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-WNS412/virtual_image.socket
163s # libfprint-context-DEBUG: created
163s # libfprint-device-DEBUG: Device reported probe completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:54.719: 41468347: ../libfprint/drivers/virtual-image.c:216
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:02:54.719: 41468360: ../libfprint/drivers/virtual-device-listener.c:153
163s # libfprint-image_device-DEBUG: Image device open completed
163s # libfprint-device-DEBUG: Device reported open completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:54.820: 41568816: ../libfprint/drivers/virtual-image.c:244
163s # libfprint-image_device-DEBUG: Image device close completed
163s # libfprint-device-DEBUG: Device reported close completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
163s ok 16 /device/sync/identify/cancelled
163s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
163s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
163s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
163s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-RVZ912/virtual_image.socket
163s # libfprint-context-DEBUG: created
163s # libfprint-device-DEBUG: Device reported probe completion
163s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
163s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:54.921: 41670168: ../libfprint/drivers/virtual-image.c:216
163s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_device_connection-DEBUG: 05:02:54.921: 41670183: ../libfprint/drivers/virtual-device-listener.c:153
164s # libfprint-image_device-DEBUG: Image device open completed
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s (/usr/libexec/installed-tests/libfprint-2/test-fp-device:2358): libfprint-virtual_image-DEBUG: 05:02:55.022: 41770684: ../libfprint/drivers/virtual-image.c:244
164s # libfprint-image_device-DEBUG: Image device close completed
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
164s ok 17 /device/sync/identify/null-prints
164s # End of identify tests
164s # End of sync tests
164s # End of device tests
164s PASS: libfprint-2/fp-device.test
164s Running test: libfprint-2/driver-synaptics.test
164s ** (umockdev-run:2421): DEBUG: 05:02:55.151: umockdev.vala:127: Created udev test bed /tmp/umockdev.WU8E22
164s ** (umockdev-run:2421): DEBUG: 05:02:55.151: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9
164s ** (umockdev-run:2421): DEBUG: 05:02:55.152: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb)
164s ** (umockdev-run:2421): DEBUG: 05:02:55.154: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WU8E22/dev/bus/usb/001/004
164s ** (umockdev-run:2421): DEBUG: 05:02:55.154: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
164s ** (umockdev-run:2421): DEBUG: 05:02:55.154: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
164s ** (umockdev-run:2421): DEBUG: 05:02:55.156: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WU8E22/dev/bus/usb/001/001
164s ** (umockdev-run:2421): DEBUG: 05:02:55.156: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0
164s ** (umockdev-run:2421): DEBUG: 05:02:55.156: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
164s (process:2425): libfprint-context-DEBUG: 05:02:55.214: Initializing FpContext (libfprint version 1.94.9+tod1)
164s (process:2425): libfprint-tod-DEBUG: 05:02:55.214: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
164s (process:2425): libfprint-context-DEBUG: 05:02:55.215: No driver found for USB device 1D6B:0002
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.215: 41964501: ../libfprint/drivers/synaptics/synaptics.c:1247
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.216: Build Time: 1596608839
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.217: Build Num: 3273255
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.217: Version: 10.1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.217: Target: 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.217: Product: 65
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.217: sequence number is 1
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.217: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.217: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.217: Device reported probe completion
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.217: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
164s (process:2425): libfprint-device-DEBUG: 05:02:55.217: Completing action FPI_DEVICE_ACTION_PROBE in idle!
164s (process:2425): libfprint-device-DEBUG: 05:02:55.217: Not updating temperature model, device can run continuously!
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.218: 41967421: ../libfprint/drivers/synaptics/synaptics.c:1407
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.219: sequence number is 2
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.219: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.219: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.219: Device reported open completion
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.219: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
164s (process:2425): libfprint-device-DEBUG: 05:02:55.219: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s (process:2425): libfprint-device-DEBUG: 05:02:55.219: Not updating temperature model, device can run continuously!
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.219: clear all prints in database
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.219: sequence number is 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.219: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.219: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.220: Deleting All Enrolled Users is 0% complete
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.220: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.220: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.220: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.220: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.220: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.220: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.221: Deleting All Enrolled Users is 100% complete
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.221: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.221: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.221: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.221: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.221: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.221: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.222: Successfully deleted all enrolled user
164s (process:2425): libfprint-device-DEBUG: 05:02:55.222: Device reported deletion completion
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.222: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
164s (process:2425): libfprint-device-DEBUG: 05:02:55.222: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
164s (process:2425): libfprint-device-DEBUG: 05:02:55.222: Not updating temperature model, device can run continuously!
164s (process:2425): libfprint-device-DEBUG: 05:02:55.222: Not updating temperature model, device can run continuously!
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.222: 41971247: ../libfprint/drivers/synaptics/synaptics.c:1018
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.222: user_id: FP1-00000000-0-00000000-nobody, finger: 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.222: sequence number is 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.222: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.222: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.223: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.223: Place Finger on the Sensor!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.223: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.223: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.223: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.223: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.223: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.223: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.223: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.223: Finger is now on the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.223: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.223: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.224: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.224: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.224: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.224: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.224: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.224: Fingerprint image capture complete!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.224: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.224: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.224: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.225: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.225: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.225: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.225: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.225: Finger is now off the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.225: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.225: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.225: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.225: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.226: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.226: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.226: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.226: Enrollment is 12 % 
164s (process:2425): libfprint-device-DEBUG: 05:02:55.226: Device reported enroll progress, reported 1 of 8 have been completed
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.226: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.226: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.226: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.227: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.227: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.227: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.227: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.227: Finger is now on the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.227: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.227: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.227: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.227: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.227: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.227: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.228: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.228: Fingerprint image capture complete!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.228: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.228: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.228: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.228: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.228: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.228: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.229: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.229: Finger is now off the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.229: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.229: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.229: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.229: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.229: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.229: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.229: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.229: Enrollment is 25 % 
164s (process:2425): libfprint-device-DEBUG: 05:02:55.229: Device reported enroll progress, reported 2 of 8 have been completed
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.229: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.230: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.230: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.230: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.230: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.230: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.230: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.230: Finger is now on the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.230: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.230: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.230: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.230: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.231: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.231: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.231: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.231: Fingerprint image capture complete!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.231: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.231: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.231: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.232: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.232: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.232: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.232: Enrollment is 37 % 
164s (process:2425): libfprint-device-DEBUG: 05:02:55.232: Device reported enroll progress, reported 3 of 8 have been completed
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.232: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.232: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.232: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.233: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.233: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.233: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.233: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.233: Finger is now off the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.233: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.233: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.233: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.233: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.233: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.233: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.233: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.234: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.234: Finger is now on the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.234: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.234: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.234: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.234: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.234: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.234: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.234: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.235: Fingerprint image capture complete!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.235: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.235: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.235: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.235: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.235: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.235: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.235: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.235: Finger is now off the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.236: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.236: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.236: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.236: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.236: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.236: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.236: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.236: Enrollment is 50 % 
164s (process:2425): libfprint-device-DEBUG: 05:02:55.236: Device reported enroll progress, reported 4 of 8 have been completed
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.236: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.237: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.237: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.237: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.237: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.237: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.237: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.237: Finger is now on the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.237: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.237: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.237: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.237: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.238: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.238: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.238: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.238: Fingerprint image capture complete!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.238: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.238: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.238: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.239: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.239: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.239: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.239: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.239: Finger is now off the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.239: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.239: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.239: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.239: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.239: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.239: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.239: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.240: Enrollment is 62 % 
164s (process:2425): libfprint-device-DEBUG: 05:02:55.240: Device reported enroll progress, reported 5 of 8 have been completed
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.240: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.240: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.240: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.240: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.240: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.240: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.241: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.241: Finger is now on the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.241: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.241: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.241: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.241: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.241: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.241: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.241: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.241: Fingerprint image capture complete!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.242: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.242: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.242: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.242: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.242: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.242: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.242: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.242: Finger is now off the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.242: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.242: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.243: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.243: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.243: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.243: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.243: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.243: Enrollment is 62 % 
164s (process:2425): libfprint-device-DEBUG: 05:02:55.243: Device reported enroll progress, reported 5 of 8 have been completed
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.243: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.244: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.244: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.244: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.244: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.244: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.244: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.244: Finger is now on the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.244: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.244: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.244: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.244: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.245: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.245: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.245: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.245: Fingerprint image capture complete!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.245: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.245: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.245: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.245: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.245: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.245: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.246: Enrollment is 75 % 
164s (process:2425): libfprint-device-DEBUG: 05:02:55.246: Device reported enroll progress, reported 6 of 8 have been completed
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.246: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.246: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.246: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.246: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.246: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.246: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.246: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.246: Finger is now off the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.246: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.246: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.247: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.247: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.247: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.247: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.247: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.247: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.247: Finger is now on the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.247: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.247: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.248: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.248: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.248: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.248: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.248: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.248: Fingerprint image capture complete!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.248: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.248: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.248: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.249: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.249: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.249: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.249: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.249: Finger is now off the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.249: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.249: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.249: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.249: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.250: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.250: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.250: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.250: Enrollment is 87 % 
164s (process:2425): libfprint-device-DEBUG: 05:02:55.250: Device reported enroll progress, reported 7 of 8 have been completed
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.250: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.250: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.250: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.250: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.251: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.251: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.251: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.251: Finger is now on the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.251: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.251: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.251: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.251: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.251: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.251: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.251: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.252: Fingerprint image capture complete!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.252: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.252: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.252: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.252: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.252: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.252: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.253: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.253: Finger is now off the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.253: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.253: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.253: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.253: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.253: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.253: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.253: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.253: Enrollment is 100 % 
164s (process:2425): libfprint-device-DEBUG: 05:02:55.253: Device reported enroll progress, reported 8 of 8 have been completed
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.253: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.254: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.254: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.254: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.254: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.254: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.254: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.254: Finger is now on the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.254: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.254: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.255: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.255: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.255: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.255: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.255: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.255: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.255: Finger is now off the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.255: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.255: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.255: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.255: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.256: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.256: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.256: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.256: Enrollment was successful!
164s (process:2425): libfprint-device-DEBUG: 05:02:55.256: Device reported enroll completion
164s (process:2425): libfprint-device-DEBUG: 05:02:55.256: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2425): libfprint-device-DEBUG: 05:02:55.256: Print for finger FP_FINGER_UNKNOWN enrolled
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.256: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
164s (process:2425): libfprint-device-DEBUG: 05:02:55.256: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
164s (process:2425): libfprint-device-DEBUG: 05:02:55.256: Not updating temperature model, device can run continuously!
164s (process:2425): libfprint-device-DEBUG: 05:02:55.256: Not updating temperature model, device can run continuously!
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.256: data is 0x2faf460
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.256: 42005272: ../libfprint/drivers/synaptics/synaptics.c:650
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.256: sequence number is 5
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.256: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.256: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.257: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.257: Place Finger on the Sensor!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.257: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.257: got suspend request
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.257: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.257: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 5
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.257: got resume request
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.257: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 6
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.257: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.257: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.258: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.258: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.258: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.258: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.258: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.258: Finger is now on the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.258: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.258: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.258: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.258: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.259: Fingerprint image capture complete!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.259: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.259: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-device-DEBUG: 05:02:55.260: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.260: Finger is now off the sensor
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.260: Received message with 0 sequence number 0x91, ignoring!
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.260: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 2
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.260: interrupt transfer done
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.260: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 3
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.260: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 4
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.260: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.260: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.260: Verify was successful! for user: FP1-00000000-0-00000000-nobody finger: 1 score: 61.800000
164s (process:2425): libfprint-device-DEBUG: 05:02:55.260: Device reported verify result
164s (process:2425): libfprint-device-DEBUG: 05:02:55.260: Device reported verify completion
164s (process:2425): libfprint-device-DEBUG: 05:02:55.260: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.260: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
164s (process:2425): libfprint-device-DEBUG: 05:02:55.260: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s (process:2425): libfprint-device-DEBUG: 05:02:55.260: Not updating temperature model, device can run continuously!
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.260: data is 0x2faf460
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.260: 42009479: ../libfprint/drivers/synaptics/synaptics.c:1127
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.260: sequence number is 6
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.260: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.261: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.261: Successfully deleted enrolled user
164s (process:2425): libfprint-device-DEBUG: 05:02:55.261: Device reported deletion completion
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.261: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
164s (process:2425): libfprint-device-DEBUG: 05:02:55.261: Completing action FPI_DEVICE_ACTION_DELETE in idle!
164s (process:2425): libfprint-device-DEBUG: 05:02:55.261: Not updating temperature model, device can run continuously!
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.261: 42010106: ../libfprint/drivers/synaptics/synaptics.c:1428
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.261: sequence number is 7
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.261: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 0
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.261: [synaptics] SYNAPTICS_CMD_NUM_STATES entering state 1
164s (process:2425): libfprint-synaptics-DEBUG: 05:02:55.262: Fingerprint sensor ready to be powered down
164s (process:2425): libfprint-device-DEBUG: 05:02:55.262: Device reported close completion
164s (process:2425): libfprint-SSM-DEBUG: 05:02:55.262: [synaptics] SYNAPTICS_CMD_NUM_STATES completed successfully
164s (process:2425): libfprint-device-DEBUG: 05:02:55.262: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s (process:2425): libfprint-device-DEBUG: 05:02:55.262: Not updating temperature model, device can run continuously!
164s enrolling
164s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbc209e00 (FpiDeviceSynaptics at 0x2fb3110)>, 1, None, None, None)
164s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbc209e00 (FpiDeviceSynaptics at 0x2fb3110)>, 2, None, None, None)
164s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbc209e00 (FpiDeviceSynaptics at 0x2fb3110)>, 3, None, None, None)
164s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbc209e00 (FpiDeviceSynaptics at 0x2fb3110)>, 4, None, None, None)
164s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbc209e00 (FpiDeviceSynaptics at 0x2fb3110)>, 5, None, None, None)
164s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbc209e00 (FpiDeviceSynaptics at 0x2fb3110)>, 5, None, None, GLib.Error('Please try again.', 'fp - device - retry - quark', 0))
164s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbc209e00 (FpiDeviceSynaptics at 0x2fb3110)>, 6, None, None, None)
164s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbc209e00 (FpiDeviceSynaptics at 0x2fb3110)>, 7, None, None, None)
164s enroll progress: (<__gi__.FpiDeviceSynaptics object at 0x3ffbc209e00 (FpiDeviceSynaptics at 0x2fb3110)>, 8, None, None, None)
164s enroll done
164s verifying
164s verify done
164s deleting
164s delete done
164s ** (umockdev-run:2421): DEBUG: 05:02:55.272: umockdev.vala:154: Removing test bed /tmp/umockdev.WU8E22
164s (umockdev-run:2421): GLib-DEBUG: 05:02:55.274: unsetenv() is not thread-safe and should not be used after threads are created
164s PASS: libfprint-2/driver-synaptics.test
164s Running test: libfprint-2/driver-egismoc-05a1.test
164s libusb: warning [libusb_exit] device 1.1 still referenced
164s ** (umockdev-run:2433): DEBUG: 05:02:55.305: umockdev.vala:127: Created udev test bed /tmp/umockdev.N4BJ22
164s ** (umockdev-run:2433): DEBUG: 05:02:55.305: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-5
164s ** (umockdev-run:2433): DEBUG: 05:02:55.307: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-5 (subsystem usb)
164s ** (umockdev-run:2433): DEBUG: 05:02:55.308: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.N4BJ22/dev/bus/usb/001/003
164s ** (umockdev-run:2433): DEBUG: 05:02:55.308: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
164s ** (umockdev-run:2433): DEBUG: 05:02:55.309: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
164s ** (umockdev-run:2433): DEBUG: 05:02:55.310: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.N4BJ22/dev/bus/usb/001/001
164s ** (umockdev-run:2433): DEBUG: 05:02:55.310: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0
164s ** (umockdev-run:2433): DEBUG: 05:02:55.311: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
164s (process:2437): libfprint-context-DEBUG: 05:02:55.371: Initializing FpContext (libfprint version 1.94.9+tod1)
164s (process:2437): libfprint-tod-DEBUG: 05:02:55.371: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.372: 42120920: ../libfprint/drivers/egismoc/egismoc.c:1597
164s (process:2437): libfprint-context-DEBUG: 05:02:55.372: No driver found for USB device 1D6B:0002
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.372: egismoc_probe enter --> 
164s (process:2437): libfprint-device-DEBUG: 05:02:55.373: Device reported probe completion
164s (process:2437): libfprint-device-DEBUG: 05:02:55.373: Completing action FPI_DEVICE_ACTION_PROBE in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.373: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.374: Opening device
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.374: [egismoc] DEV_INIT_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.374: [egismoc] DEV_INIT_STATES entering state 1
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.374: [egismoc] DEV_INIT_STATES entering state 2
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.375: [egismoc] DEV_INIT_STATES entering state 3
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.375: [egismoc] DEV_INIT_STATES entering state 4
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.375: [egismoc] DEV_INIT_STATES entering state 5
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.375: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.375: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.375: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.376: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.376: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.376: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.376: Firmware version callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.376: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.376: Device firmware version is 9050.1.2.13
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.376: [egismoc] DEV_INIT_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.376: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.376: Device reported open completion
164s (process:2437): libfprint-device-DEBUG: 05:02:55.376: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.376: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.377: List
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.377: [egismoc] LIST_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.377: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.377: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.377: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.377: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.377: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.377: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.377: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.377: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.377: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.377: Device fingerprint 3: FP1-20231209-2-04EFB67C-root
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.377: Number of currently enrolled fingerprints on the device is 3
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.377: [egismoc] LIST_STATES entering state 1
164s (process:2437): libfprint-device-DEBUG: 05:02:55.377: Device reported listing completion
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.377: [egismoc] LIST_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.377: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.377: Completing action FPI_DEVICE_ACTION_LIST in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.378: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.378: Clear storage
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.378: [egismoc] DELETE_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.378: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.378: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.378: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.378: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.378: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.378: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.378: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.378: Device fingerprint 1: FP1-20231209-3-A9E16FBD-root
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.378: Device fingerprint 2: FP1-20231209-1-85DC4FAC-root
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.378: Device fingerprint 3: FP1-20231209-2-04EFB67C-root
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.378: Number of currently enrolled fingerprints on the device is 3
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.378: [egismoc] DELETE_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.378: Get delete command
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.378: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.378: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.378: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.379: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.379: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.379: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.379: Delete callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.379: Response prefix valid: yes
164s (process:2437): libfprint-device-DEBUG: 05:02:55.379: Device reported deletion completion
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.379: [egismoc] DELETE_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.379: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.379: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.379: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.379: List
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.379: [egismoc] LIST_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.379: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.379: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.379: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.379: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.380: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.380: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.380: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.380: Number of currently enrolled fingerprints on the device is 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.380: [egismoc] LIST_STATES entering state 1
164s (process:2437): libfprint-device-DEBUG: 05:02:55.380: Device reported listing completion
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.380: [egismoc] LIST_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.380: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.380: Completing action FPI_DEVICE_ACTION_LIST in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.380: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s (process:2437): libfprint-device-DEBUG: 05:02:55.380: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.380: Enroll
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.380: [egismoc] ENROLL_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.380: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.380: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.380: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.381: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.381: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.381: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.381: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.381: Number of currently enrolled fingerprints on the device is 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.381: [egismoc] ENROLL_STATES entering state 1
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.381: [egismoc] ENROLL_STATES entering state 2
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.381: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.381: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.381: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.382: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.382: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.382: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.382: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.382: [egismoc] ENROLL_STATES entering state 3
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.382: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.382: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.382: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.382: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.383: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.383: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.383: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.383: [egismoc] ENROLL_STATES entering state 4
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.383: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.383: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.383: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.383: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.383: [egismoc] ENROLL_STATES entering state 5
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.383: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.383: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.383: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.383: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.384: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.384: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.384: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.384: [egismoc] ENROLL_STATES entering state 6
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.384: Get check command
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.384: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.384: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.384: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.384: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.384: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.384: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.384: Enroll check callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.384: Response suffix valid: yes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.384: [egismoc] ENROLL_STATES entering state 7
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.384: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.384: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.384: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.385: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.385: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.385: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.385: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.385: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.385: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.385: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.385: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.385: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.385: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.385: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.385: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.385: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.385: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.385: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.385: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.386: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.387: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.387: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.387: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.387: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.387: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.387: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.387: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.387: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.387: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.387: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.387: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.387: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.387: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.388: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.388: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.388: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.388: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.388: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.388: Partial capture successful. Please touch the sensor again (1/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.388: Device reported enroll progress, reported 1 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.388: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.388: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.388: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.388: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.388: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.388: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.388: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.388: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.388: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.388: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.388: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.388: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.389: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.389: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.389: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.389: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.389: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.389: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.389: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.389: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.389: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.389: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.389: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.389: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.389: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.390: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.390: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.390: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.390: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.390: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.390: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.390: Partial capture successful. Please touch the sensor again (2/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.390: Device reported enroll progress, reported 2 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.390: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.390: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.390: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.390: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.390: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.390: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.390: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.390: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.390: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.390: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.390: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.390: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.391: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.391: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.391: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.391: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.391: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.391: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.391: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.391: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.391: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.391: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.391: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.391: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.391: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.392: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.392: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.392: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.392: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.392: Response prefix valid: NO
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.392: Response prefix valid: NO
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.392: Response prefix valid: yes
164s (process:2437): libfprint-device-DEBUG: 05:02:55.392: Device reported enroll progress, reported 2 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.392: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.392: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.392: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.392: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.392: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.393: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.393: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.393: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.393: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.393: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.393: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.393: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.393: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.393: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.393: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.393: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.393: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.393: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.393: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.394: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.394: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.394: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.394: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.394: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.394: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.394: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.394: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.394: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.394: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.394: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.394: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.394: Partial capture successful. Please touch the sensor again (3/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.394: Device reported enroll progress, reported 3 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.394: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.394: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.394: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.394: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.395: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.395: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.395: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.395: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.395: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.395: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.395: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.395: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.395: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.395: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.395: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.395: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.395: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.395: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.395: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.396: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.396: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.396: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.396: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.396: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.396: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.396: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.396: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.396: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.396: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.396: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.396: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.396: Partial capture successful. Please touch the sensor again (4/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.396: Device reported enroll progress, reported 4 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.396: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.396: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.396: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.396: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.396: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.397: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.397: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.397: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.397: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.397: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.397: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.397: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.397: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.397: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.397: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.397: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.397: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.397: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.397: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.398: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.398: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.398: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.398: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.398: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.398: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.398: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.398: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.398: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.398: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.398: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.398: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.398: Partial capture successful. Please touch the sensor again (5/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.398: Device reported enroll progress, reported 5 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.398: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.398: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.398: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.398: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.399: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.399: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.399: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.399: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.399: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.399: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.399: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.399: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.399: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.400: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.400: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.400: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.400: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.400: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.400: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.400: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.400: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.400: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.400: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.400: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.400: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.400: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.401: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.401: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.401: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.401: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.401: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.401: Partial capture successful. Please touch the sensor again (6/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.401: Device reported enroll progress, reported 6 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.401: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.401: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.401: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.401: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.401: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.401: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.401: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.401: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.401: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.401: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.401: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.401: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.401: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.402: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.402: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.402: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.402: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.402: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.402: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.402: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.402: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.402: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.402: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.402: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.402: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.402: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.402: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.402: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.402: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.402: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.402: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.403: Partial capture successful. Please touch the sensor again (7/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.403: Device reported enroll progress, reported 7 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.403: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.403: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.403: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.403: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.403: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.403: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.403: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.403: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.403: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.403: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.403: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.403: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.403: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.404: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.404: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.404: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.404: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.404: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.404: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.404: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.404: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.404: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.404: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.404: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.404: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.404: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.404: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.404: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.404: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.404: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.404: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.404: Partial capture successful. Please touch the sensor again (8/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.404: Device reported enroll progress, reported 8 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.404: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.404: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.404: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.404: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.405: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.405: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.405: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.405: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.405: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.405: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.405: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.405: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.405: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.406: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.406: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.406: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.406: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.406: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.406: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.406: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.406: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.406: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.406: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.406: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.406: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.406: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.406: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.406: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.406: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.407: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.407: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.407: Partial capture successful. Please touch the sensor again (9/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.407: Device reported enroll progress, reported 9 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.407: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.407: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.407: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.407: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.407: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.407: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.407: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.407: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.407: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.407: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.407: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.407: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.407: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.408: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.408: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.408: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.408: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.408: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.408: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.408: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.408: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.408: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.408: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.408: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.408: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.408: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.409: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.409: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.409: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.409: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.409: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.409: Partial capture successful. Please touch the sensor again (10/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.409: Device reported enroll progress, reported 10 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.409: [egismoc] ENROLL_STATES entering state 12
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.409: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.409: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.409: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.409: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.409: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.409: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.409: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.409: [egismoc] ENROLL_STATES entering state 13
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.409: New fingerprint ID: FP1-00000000-2-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.409: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.409: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.409: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.410: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.410: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.410: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.410: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.410: [egismoc] ENROLL_STATES entering state 14
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.410: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.410: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.410: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.410: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.410: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.410: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.410: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.410: [egismoc] ENROLL_STATES entering state 15
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.410: Enrollment was successful!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.410: Device reported enroll completion
164s (process:2437): libfprint-device-DEBUG: 05:02:55.410: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2437): libfprint-device-DEBUG: 05:02:55.410: Print for finger FP_FINGER_LEFT_INDEX enrolled
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.410: [egismoc] ENROLL_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.410: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.410: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.410: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.410: List
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.410: [egismoc] LIST_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.410: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.410: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.410: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.411: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.411: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.411: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.411: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.411: Device fingerprint 1: FP1-00000000-2-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.411: Number of currently enrolled fingerprints on the device is 1
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.411: [egismoc] LIST_STATES entering state 1
164s (process:2437): libfprint-device-DEBUG: 05:02:55.411: Device reported listing completion
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.411: [egismoc] LIST_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.411: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.411: Completing action FPI_DEVICE_ACTION_LIST in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.411: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-device-DEBUG: 05:02:55.411: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.411: Identify or Verify
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.411: [egismoc] IDENTIFY_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.411: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.411: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.411: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.412: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.412: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.412: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.412: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.412: Device fingerprint 1: FP1-00000000-2-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.412: Number of currently enrolled fingerprints on the device is 1
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.412: [egismoc] IDENTIFY_STATES entering state 1
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.412: [egismoc] IDENTIFY_STATES entering state 2
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.412: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.412: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.412: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.412: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.413: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.413: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.413: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.413: [egismoc] IDENTIFY_STATES entering state 3
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.413: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.413: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.413: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.413: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.413: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.413: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.413: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.413: [egismoc] IDENTIFY_STATES entering state 4
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.413: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.413: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.414: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.414: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.414: [egismoc] IDENTIFY_STATES entering state 5
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.414: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.414: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.414: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.414: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.414: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.414: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.414: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.414: [egismoc] IDENTIFY_STATES entering state 6
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.414: Get check command
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.414: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.414: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.414: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.415: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.415: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.415: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.415: Identify check callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.415: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.415: Identify successful for: FP1-00000000-2-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.415: Verifying against: FP1-00000000-2-00000000-nobody
164s (process:2437): libfprint-device-DEBUG: 05:02:55.415: Device reported verify result
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.415: [egismoc] IDENTIFY_STATES entering state 7
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.415: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.415: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.415: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.415: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.415: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.415: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.415: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.415: [egismoc] IDENTIFY_STATES entering state 8
164s (process:2437): libfprint-device-DEBUG: 05:02:55.415: Device reported verify completion
164s (process:2437): libfprint-device-DEBUG: 05:02:55.415: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.415: [egismoc] IDENTIFY_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.415: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.416: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.416: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-device-DEBUG: 05:02:55.416: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.416: Identify or Verify
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.416: [egismoc] IDENTIFY_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.416: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.416: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.416: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.416: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.416: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.416: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.416: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.416: Device fingerprint 1: FP1-00000000-2-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.416: Number of currently enrolled fingerprints on the device is 1
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.416: [egismoc] IDENTIFY_STATES entering state 1
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.416: [egismoc] IDENTIFY_STATES entering state 2
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.416: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.416: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.416: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.417: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.417: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.417: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.417: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.417: [egismoc] IDENTIFY_STATES entering state 3
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.417: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.417: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.417: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.417: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.417: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.417: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.417: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.417: [egismoc] IDENTIFY_STATES entering state 4
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.417: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.417: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.418: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.418: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.418: [egismoc] IDENTIFY_STATES entering state 5
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.418: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.418: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.418: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.418: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.418: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.418: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.418: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.418: [egismoc] IDENTIFY_STATES entering state 6
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.418: Get check command
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.418: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.418: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.418: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.419: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.419: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.419: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.419: Identify check callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.419: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.419: Identify successful for: FP1-00000000-2-00000000-nobody
164s (process:2437): libfprint-device-DEBUG: 05:02:55.419: Device reported identify result
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.419: [egismoc] IDENTIFY_STATES entering state 7
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.419: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.419: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.419: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.419: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.420: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.420: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.420: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.420: [egismoc] IDENTIFY_STATES entering state 8
164s (process:2437): libfprint-device-DEBUG: 05:02:55.420: Device reported identify completion
164s (process:2437): libfprint-device-DEBUG: 05:02:55.420: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.420: [egismoc] IDENTIFY_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.420: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.420: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.420: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-device-DEBUG: 05:02:55.420: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.420: Enroll
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.420: [egismoc] ENROLL_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.420: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.420: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.420: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.420: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.421: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.421: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.421: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.421: Device fingerprint 1: FP1-00000000-2-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.421: Number of currently enrolled fingerprints on the device is 1
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.421: [egismoc] ENROLL_STATES entering state 1
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.421: [egismoc] ENROLL_STATES entering state 2
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.421: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.421: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.421: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.421: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.421: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.421: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.421: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.421: [egismoc] ENROLL_STATES entering state 3
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.421: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.421: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.421: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.421: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.422: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.422: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.422: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.422: [egismoc] ENROLL_STATES entering state 4
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.422: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.422: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.422: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.422: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.422: [egismoc] ENROLL_STATES entering state 5
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.422: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.422: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.422: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.422: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.423: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.423: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.423: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.423: [egismoc] ENROLL_STATES entering state 6
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.423: Get check command
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.423: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.423: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.423: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.423: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.423: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.423: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.423: Enroll check callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.423: Response suffix valid: NO
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.423: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.423: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.423: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.423: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL
164s (process:2437): libfprint-device-DEBUG: 05:02:55.423: Device reported enroll completion
164s (process:2437): libfprint-device-DEBUG: 05:02:55.423: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2437): libfprint-device-DEBUG: 05:02:55.423: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.423: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.423: List
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.423: [egismoc] LIST_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.423: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.423: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.423: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.424: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.424: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.424: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.424: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.424: Device fingerprint 1: FP1-00000000-2-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.424: Number of currently enrolled fingerprints on the device is 1
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.424: [egismoc] LIST_STATES entering state 1
164s (process:2437): libfprint-device-DEBUG: 05:02:55.424: Device reported listing completion
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.424: [egismoc] LIST_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.424: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.424: Completing action FPI_DEVICE_ACTION_LIST in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.424: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-device-DEBUG: 05:02:55.424: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.424: Enroll
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.424: [egismoc] ENROLL_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.424: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.424: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.424: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.424: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.425: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.425: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.425: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.425: Device fingerprint 1: FP1-00000000-2-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.425: Number of currently enrolled fingerprints on the device is 1
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.425: [egismoc] ENROLL_STATES entering state 1
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.425: [egismoc] ENROLL_STATES entering state 2
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.425: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.425: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.425: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.425: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.425: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.425: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.425: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.425: [egismoc] ENROLL_STATES entering state 3
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.425: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.425: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.425: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.426: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.426: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.426: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.426: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.426: [egismoc] ENROLL_STATES entering state 4
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.426: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.426: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.426: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.426: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.426: [egismoc] ENROLL_STATES entering state 5
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.426: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.426: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.426: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.427: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.427: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.427: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.427: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.427: [egismoc] ENROLL_STATES entering state 6
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.427: Get check command
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.427: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.427: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.427: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.427: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.428: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.428: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.428: Enroll check callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.428: Response suffix valid: yes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.428: [egismoc] ENROLL_STATES entering state 7
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.428: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.428: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.428: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.428: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.428: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.428: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.428: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.428: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.428: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.428: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.428: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.428: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.429: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.429: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.429: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.429: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.429: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.429: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.429: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.429: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.429: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.429: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.429: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.429: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.429: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.429: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.430: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.430: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.430: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.430: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.430: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.430: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.430: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.430: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.430: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.430: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.430: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.430: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.430: Partial capture successful. Please touch the sensor again (1/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.430: Device reported enroll progress, reported 1 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.430: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.430: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.430: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.430: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.431: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.431: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.431: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.431: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.431: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.431: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.431: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.431: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.431: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.432: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.432: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.432: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.432: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.432: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.432: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.432: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.432: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.432: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.432: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.432: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.432: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.432: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.432: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.432: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.432: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.432: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.432: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.432: Partial capture successful. Please touch the sensor again (2/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.432: Device reported enroll progress, reported 2 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.432: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.432: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.432: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.432: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.433: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.433: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.433: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.433: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.433: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.433: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.433: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.433: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.433: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.433: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.434: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.434: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.434: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.434: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.434: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.434: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.434: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.434: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.434: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.434: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.434: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.434: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.434: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.434: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.434: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.434: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.434: Response suffix valid: NO
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.434: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.434: Response suffix valid: yes
164s (process:2437): libfprint-device-DEBUG: 05:02:55.434: Device reported enroll progress, reported 2 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.434: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.434: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.434: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.434: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.435: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.435: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.435: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.435: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.435: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.435: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.435: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.435: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.435: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.436: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.436: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.436: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.436: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.436: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.436: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.436: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.436: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.436: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.436: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.436: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.436: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.436: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.437: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.437: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.437: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.437: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.437: Response suffix valid: NO
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.437: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.437: Response suffix valid: yes
164s (process:2437): libfprint-device-DEBUG: 05:02:55.437: Device reported enroll progress, reported 2 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.437: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.437: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.437: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.437: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.437: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.437: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.437: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.437: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.437: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.437: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.437: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.437: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.438: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.438: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.438: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.438: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.438: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.438: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.438: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.438: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.438: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.438: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.438: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.438: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.438: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.439: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.439: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.439: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.439: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.439: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.439: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.439: Partial capture successful. Please touch the sensor again (3/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.439: Device reported enroll progress, reported 3 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.439: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.439: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.439: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.439: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.439: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.440: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.440: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.440: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.440: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.440: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.440: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.440: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.440: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.440: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.440: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.440: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.440: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.440: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.440: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.441: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.441: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.441: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.441: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.441: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.441: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.441: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.441: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.441: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.441: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.441: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.441: Response suffix valid: NO
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.441: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.441: Response suffix valid: yes
164s (process:2437): libfprint-device-DEBUG: 05:02:55.441: Device reported enroll progress, reported 3 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.441: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.441: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.441: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.441: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.442: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.442: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.442: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.442: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.442: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.442: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.442: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.442: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.442: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.443: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.443: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.443: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.443: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.443: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.443: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.443: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.443: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.443: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.443: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.443: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.443: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.443: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.444: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.444: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.444: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.444: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.444: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.444: Partial capture successful. Please touch the sensor again (4/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.444: Device reported enroll progress, reported 4 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.444: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.444: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.444: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.444: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.444: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.444: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.444: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.444: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.444: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.444: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.444: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.444: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.445: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.445: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.445: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.445: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.445: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.445: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.445: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.445: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.445: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.445: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.445: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.445: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.445: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.445: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.446: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.446: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.446: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.446: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.446: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.446: Partial capture successful. Please touch the sensor again (5/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.446: Device reported enroll progress, reported 5 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.446: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.446: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.446: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.446: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.446: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.446: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.446: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.446: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.446: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.446: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.446: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.446: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.447: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.447: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.447: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.447: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.447: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.447: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.447: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.447: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.447: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.447: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.447: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.447: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.447: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.447: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.448: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.448: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.448: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.448: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.448: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.448: Partial capture successful. Please touch the sensor again (6/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.448: Device reported enroll progress, reported 6 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.448: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.448: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.448: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.448: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.448: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.448: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.448: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.448: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.448: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.448: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.448: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.448: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.449: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.449: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.449: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.449: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.449: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.449: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.449: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.449: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.449: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.449: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.449: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.449: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.449: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.450: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.450: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.450: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.450: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.450: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.450: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.450: Partial capture successful. Please touch the sensor again (7/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.450: Device reported enroll progress, reported 7 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.450: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.450: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.450: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.450: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.450: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.451: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.451: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.451: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.451: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.451: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.451: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.451: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.451: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.451: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.451: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.451: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.451: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.451: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.451: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.452: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.452: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.452: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.452: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.452: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.452: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.452: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.452: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.452: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.452: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.452: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.452: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.452: Partial capture successful. Please touch the sensor again (8/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.452: Device reported enroll progress, reported 8 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.452: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.452: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.452: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.452: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.453: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.453: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.453: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.453: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.453: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.453: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.453: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.453: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.453: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.453: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.453: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.453: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.453: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.453: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.453: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.454: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.454: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.454: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.454: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.454: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.454: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.454: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.454: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.454: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.454: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.454: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.454: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.454: Partial capture successful. Please touch the sensor again (9/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.454: Device reported enroll progress, reported 9 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.455: [egismoc] ENROLL_STATES entering state 8
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.455: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.455: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.455: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.455: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.455: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.455: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.455: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.455: [egismoc] ENROLL_STATES entering state 9
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.455: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.455: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.455: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.455: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.456: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.456: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.456: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.456: [egismoc] ENROLL_STATES entering state 10
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.456: Wait for finger on sensor
164s (process:2437): libfprint-device-DEBUG: 05:02:55.456: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.456: Finger on sensor callback
164s (process:2437): libfprint-device-DEBUG: 05:02:55.456: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.456: [egismoc] ENROLL_STATES entering state 11
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.456: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.456: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.456: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.456: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.457: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.457: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.457: Read capture callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.457: Response prefix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.457: Response suffix valid: yes
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.457: Partial capture successful. Please touch the sensor again (10/10)
164s (process:2437): libfprint-device-DEBUG: 05:02:55.457: Device reported enroll progress, reported 10 of 10 have been completed
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.457: [egismoc] ENROLL_STATES entering state 12
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.457: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.457: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.457: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.457: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.457: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.457: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.457: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.457: [egismoc] ENROLL_STATES entering state 13
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.457: New fingerprint ID: FP1-00000000-7-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.457: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.457: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.457: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.457: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.458: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.458: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.458: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.458: [egismoc] ENROLL_STATES entering state 14
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.458: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.458: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.458: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.458: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.458: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.458: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.458: Task SSM next state callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.458: [egismoc] ENROLL_STATES entering state 15
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.458: Enrollment was successful!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.458: Device reported enroll completion
164s (process:2437): libfprint-device-DEBUG: 05:02:55.458: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2437): libfprint-device-DEBUG: 05:02:55.458: Print for finger FP_FINGER_RIGHT_INDEX enrolled
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.458: [egismoc] ENROLL_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.458: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.458: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.458: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.458: List
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.458: [egismoc] LIST_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.458: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.458: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.458: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.459: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.459: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.459: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.459: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.459: Device fingerprint 1: FP1-00000000-2-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.459: Device fingerprint 2: FP1-00000000-7-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.459: Number of currently enrolled fingerprints on the device is 2
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.459: [egismoc] LIST_STATES entering state 1
164s (process:2437): libfprint-device-DEBUG: 05:02:55.459: Device reported listing completion
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.459: [egismoc] LIST_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.459: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.459: Completing action FPI_DEVICE_ACTION_LIST in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.459: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.459: Delete
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.459: [egismoc] DELETE_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.459: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.459: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.459: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.459: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.460: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: Device fingerprint 1: FP1-00000000-2-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: Device fingerprint 2: FP1-00000000-7-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: Number of currently enrolled fingerprints on the device is 2
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.460: [egismoc] DELETE_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: Get delete command
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody)
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.460: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.460: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.460: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: Delete callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: Response prefix valid: yes
164s (process:2437): libfprint-device-DEBUG: 05:02:55.460: Device reported deletion completion
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.460: [egismoc] DELETE_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.460: Completing action FPI_DEVICE_ACTION_DELETE in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.460: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: List
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.460: [egismoc] LIST_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.460: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.460: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.461: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.461: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.461: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.461: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.461: Device fingerprint 1: FP1-00000000-7-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.461: Number of currently enrolled fingerprints on the device is 1
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.461: [egismoc] LIST_STATES entering state 1
164s (process:2437): libfprint-device-DEBUG: 05:02:55.461: Device reported listing completion
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.461: [egismoc] LIST_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.461: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.461: Completing action FPI_DEVICE_ACTION_LIST in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.461: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.461: Clear storage
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.461: [egismoc] DELETE_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.461: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.461: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.461: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.461: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.462: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.462: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.462: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.462: Device fingerprint 1: FP1-00000000-7-00000000-nobody
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.462: Number of currently enrolled fingerprints on the device is 1
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.462: [egismoc] DELETE_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.462: Get delete command
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.462: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.462: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.462: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.462: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.462: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.462: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.462: Delete callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.462: Response prefix valid: yes
164s (process:2437): libfprint-device-DEBUG: 05:02:55.462: Device reported deletion completion
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.462: [egismoc] DELETE_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.462: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.462: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.462: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.462: List
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.462: [egismoc] LIST_STATES entering state 0
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.462: Execute command and get response
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.462: Get check bytes
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.462: [egismoc] CMD_STATES entering state 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.463: [egismoc] CMD_STATES entering state 1
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.463: Command receive callback
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.463: [egismoc] CMD_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.463: List callback
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.463: Number of currently enrolled fingerprints on the device is 0
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.463: [egismoc] LIST_STATES entering state 1
164s (process:2437): libfprint-device-DEBUG: 05:02:55.463: Device reported listing completion
164s (process:2437): libfprint-SSM-DEBUG: 05:02:55.463: [egismoc] LIST_STATES completed successfully
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.463: Task SSM done
164s (process:2437): libfprint-device-DEBUG: 05:02:55.463: Completing action FPI_DEVICE_ACTION_LIST in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.463: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.463: Closing device
164s (process:2437): libfprint-egismoc-DEBUG: 05:02:55.463: Cancel
164s (process:2437): libfprint-device-DEBUG: 05:02:55.463: Device reported close completion
164s (process:2437): libfprint-device-DEBUG: 05:02:55.463: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s (process:2437): libfprint-device-DEBUG: 05:02:55.463: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s listing - device should have prints
164s clear device storage
164s clear done
164s listing - device should be empty
164s enrolling
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 1, <FPrint.Print object at 0x3ffbc90fcc0 (FpPrint at 0x2508120)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 2, <FPrint.Print object at 0x3ffbc90fcc0 (FpPrint at 0x2508120)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 2, None, None, GLib.Error('Your device is having trouble recognizing you. Make sure your sensor is clean.', 'fp - device - retry - quark', 3))
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 3, <FPrint.Print object at 0x3ffbc90fcc0 (FpPrint at 0x2508120)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 4, <FPrint.Print object at 0x3ffbc90fcc0 (FpPrint at 0x2508120)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 5, <FPrint.Print object at 0x3ffbc90fcc0 (FpPrint at 0x2508120)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 6, <FPrint.Print object at 0x3ffbc90fcc0 (FpPrint at 0x2508120)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 7, <FPrint.Print object at 0x3ffbc90fcc0 (FpPrint at 0x2508120)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 8, <FPrint.Print object at 0x3ffbc90fcc0 (FpPrint at 0x2508120)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 9, <FPrint.Print object at 0x3ffbc90fcc0 (FpPrint at 0x2508120)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 10, <FPrint.Print object at 0x3ffbc90fcc0 (FpPrint at 0x2508120)>, None, None)
164s enroll done
164s listing - device should have 1 print
164s verifying
164s verify done
164s async identifying
164s indentification_done:  <FPrint.Print object at 0x3ffbc912d40 (FpPrint at 0x25147d0)> <FPrint.Print object at 0x3ffbc912d80 (FpPrint at 0x2518580)>
164s try to enroll duplicate
164s duplicate enroll attempt done
164s listing - device should still only have 1 print
164s enroll new finger
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 1, <FPrint.Print object at 0x3ffbc913600 (FpPrint at 0x2514d90)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 2, <FPrint.Print object at 0x3ffbc913600 (FpPrint at 0x2514d90)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 3, <FPrint.Print object at 0x3ffbc913600 (FpPrint at 0x2514d90)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 4, <FPrint.Print object at 0x3ffbc913600 (FpPrint at 0x2514d90)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 5, <FPrint.Print object at 0x3ffbc913600 (FpPrint at 0x2514d90)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 6, <FPrint.Print object at 0x3ffbc913600 (FpPrint at 0x2514d90)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 7, <FPrint.Print object at 0x3ffbc913600 (FpPrint at 0x2514d90)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 8, <FPrint.Print object at 0x3ffbc913600 (FpPrint at 0x2514d90)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 9, <FPrint.Print object at 0x3ffbc913600 (FpPrint at 0x2514d90)>, None, None)
164s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffbc90e540 (FpiDeviceEgisMoc at 0x2512bf0)>, 10, <FPrint.Print object at 0x3ffbc913600 (FpPrint at 0x2514d90)>, None, None)
164s enroll new finger done
164s listing - device should have 2 prints
164s deleting first print
164s delete done
164s listing - device should only have second print
164s clear device storage
164s clear done
164s listing - device should be empty
164s ** (umockdev-run:2433): DEBUG: 05:02:55.475: umockdev.vala:154: Removing test bed /tmp/umockdev.N4BJ22
164s (umockdev-run:2433): GLib-DEBUG: 05:02:55.477: unsetenv() is not thread-safe and should not be used after threads are created
164s PASS: libfprint-2/driver-egismoc-05a1.test
164s Running test: libfprint-2/driver-realtek.test
164s ** (umockdev-run:2445): DEBUG: 05:02:55.509: umockdev.vala:127: Created udev test bed /tmp/umockdev.UT7J22
164s ** (umockdev-run:2445): DEBUG: 05:02:55.509: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-8
164s ** (umockdev-run:2445): DEBUG: 05:02:55.510: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-8 (subsystem usb)
164s ** (umockdev-run:2445): DEBUG: 05:02:55.512: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.UT7J22/dev/bus/usb/001/025
164s ** (umockdev-run:2445): DEBUG: 05:02:55.512: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
164s ** (umockdev-run:2445): DEBUG: 05:02:55.513: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
164s ** (umockdev-run:2445): DEBUG: 05:02:55.514: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.UT7J22/dev/bus/usb/001/001
164s ** (umockdev-run:2445): DEBUG: 05:02:55.514: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0
164s ** (umockdev-run:2445): DEBUG: 05:02:55.515: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
164s (process:2449): libfprint-context-DEBUG: 05:02:55.572: Initializing FpContext (libfprint version 1.94.9+tod1)
164s (process:2449): libfprint-tod-DEBUG: 05:02:55.573: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
164s (process:2449): libfprint-context-DEBUG: 05:02:55.574: No driver found for USB device 1D6B:0002
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.574: 42322893: ../libfprint/drivers/realtek/realtek.c:1224
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.575: Device name: Realtek USB2.0 Finger Print Bridge
164s (process:2449): libfprint-device-DEBUG: 05:02:55.575: Device reported probe completion
164s (process:2449): libfprint-device-DEBUG: 05:02:55.575: Completing action FPI_DEVICE_ACTION_PROBE in idle!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.575: Not updating temperature model, device can run continuously!
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.576: 42325295: ../libfprint/drivers/realtek/realtek.c:1269
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.577: [realtek] Init entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.577: [realtek] Init entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.577: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.577: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.577: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.577: [realtek] Init entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.577: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.578: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.578: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.578: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.578: [realtek] Init completed successfully
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.578: Init complete!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.578: Device reported open completion
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.578: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-device-DEBUG: 05:02:55.578: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.578: Not updating temperature model, device can run continuously!
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.578: 42327584: ../libfprint/drivers/realtek/realtek.c:1332
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.578: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.579: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.579: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.579: Successfully cleared storage
164s (process:2449): libfprint-device-DEBUG: 05:02:55.579: Device reported deletion completion
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.579: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-device-DEBUG: 05:02:55.579: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.579: Not updating temperature model, device can run continuously!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.580: Not updating temperature model, device can run continuously!
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.580: 42328739: ../libfprint/drivers/realtek/realtek.c:1201
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.580: [realtek] Enroll entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.580: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.580: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.580: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.580: [realtek] Enroll entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.580: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.581: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.581: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.581: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.581: [realtek] Enroll entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.581: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.581: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.581: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.581: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.581: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.581: [realtek] Enroll entering state 3
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.582: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.582: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.582: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.582: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.582: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.582: [realtek] Enroll entering state 4
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.582: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.582: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.582: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.583: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.583: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2449): libfprint-device-DEBUG: 05:02:55.583: Device reported enroll progress, reported 1 of 8 have been completed
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.583: [realtek] Enroll entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.583: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.583: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.583: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.583: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.583: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.583: [realtek] Enroll entering state 3
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.583: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.584: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.584: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.584: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.584: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.584: [realtek] Enroll entering state 4
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.584: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.584: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.584: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.585: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.585: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2449): libfprint-device-DEBUG: 05:02:55.585: Device reported enroll progress, reported 2 of 8 have been completed
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.585: [realtek] Enroll entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.585: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.585: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.585: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.585: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.585: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.585: [realtek] Enroll entering state 3
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.585: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.586: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.586: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.586: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.586: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.586: [realtek] Enroll entering state 4
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.586: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.586: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.586: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.587: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.587: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2449): libfprint-device-DEBUG: 05:02:55.587: Device reported enroll progress, reported 3 of 8 have been completed
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.587: [realtek] Enroll entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.587: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.587: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.587: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.587: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.587: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.588: [realtek] Enroll entering state 3
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.588: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.588: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.588: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.588: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.588: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.588: [realtek] Enroll entering state 4
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.588: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.589: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.589: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.589: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.589: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2449): libfprint-device-DEBUG: 05:02:55.589: Device reported enroll progress, reported 4 of 8 have been completed
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.589: [realtek] Enroll entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.589: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.589: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.589: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.589: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.589: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.590: [realtek] Enroll entering state 3
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.590: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.590: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.590: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.590: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.590: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.590: [realtek] Enroll entering state 4
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.590: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.590: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.591: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.591: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.591: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2449): libfprint-device-DEBUG: 05:02:55.591: Device reported enroll progress, reported 5 of 8 have been completed
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.591: [realtek] Enroll entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.591: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.591: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.591: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.591: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.591: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.591: [realtek] Enroll entering state 3
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.592: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.592: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.592: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.592: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.592: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.592: [realtek] Enroll entering state 4
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.592: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.592: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.592: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.593: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.593: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2449): libfprint-device-DEBUG: 05:02:55.593: Device reported enroll progress, reported 6 of 8 have been completed
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.593: [realtek] Enroll entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.593: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.593: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.593: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.593: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.593: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.593: [realtek] Enroll entering state 3
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.593: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.593: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.593: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.594: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.594: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.594: [realtek] Enroll entering state 4
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.594: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.594: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.594: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.594: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.595: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2449): libfprint-device-DEBUG: 05:02:55.595: Device reported enroll progress, reported 7 of 8 have been completed
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.595: [realtek] Enroll entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.595: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.595: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.595: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.595: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.595: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.595: [realtek] Enroll entering state 3
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.595: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.595: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.595: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.595: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.596: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.596: [realtek] Enroll entering state 4
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.596: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.596: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.596: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.596: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.597: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2449): libfprint-device-DEBUG: 05:02:55.597: Device reported enroll progress, reported 8 of 8 have been completed
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.597: [realtek] Enroll entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.597: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.597: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.597: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.597: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.597: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.597: [realtek] Enroll entering state 3
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.597: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.597: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.597: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.597: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.598: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.598: [realtek] Enroll entering state 4
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.598: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.598: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.598: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.598: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.598: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.598: [realtek] Enroll entering state 5
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.598: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.599: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.599: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.599: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.599: [realtek] Enroll entering state 6
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.599: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.599: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.599: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.599: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.600: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.600: [realtek] Enroll completed successfully
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.600: Enrollment complete!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.600: Device reported enroll completion
164s (process:2449): libfprint-device-DEBUG: 05:02:55.600: Print for finger FP_FINGER_UNKNOWN enrolled
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.600: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-device-DEBUG: 05:02:55.600: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.600: Not updating temperature model, device can run continuously!
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.600: 42349071: ../libfprint/drivers/realtek/realtek.c:1344
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.600: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.600: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.600: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.601: Query templates complete!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.601: Device reported listing completion
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.601: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-device-DEBUG: 05:02:55.601: Completing action FPI_DEVICE_ACTION_LIST in idle!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.601: Not updating temperature model, device can run continuously!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.601: Not updating temperature model, device can run continuously!
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.601: 42349999: ../libfprint/drivers/realtek/realtek.c:1177
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.601: [realtek] Verify & Identify entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.601: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.601: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.601: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.602: [realtek] Verify & Identify entering state 1
164s (process:2449): libfprint-device-DEBUG: 05:02:55.602: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.602: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.602: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.602: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.602: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.602: [realtek] Verify & Identify entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.602: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.602: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.602: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.602: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.603: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.603: [realtek] Verify & Identify entering state 3
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.603: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.603: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.603: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.603: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.603: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.603: [realtek] Verify & Identify entering state 4
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.603: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.604: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.604: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.604: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.604: Device reported verify result
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.604: [realtek] Verify & Identify entering state 5
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.604: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.604: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.604: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.604: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.605: [realtek] Verify & Identify completed successfully
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.605: Verify complete!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.605: Device reported verify completion
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.605: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-device-DEBUG: 05:02:55.605: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.605: Not updating temperature model, device can run continuously!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.605: Not updating temperature model, device can run continuously!
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.605: 42354128: ../libfprint/drivers/realtek/realtek.c:1177
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.605: [realtek] Verify & Identify entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.605: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.605: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.605: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.606: [realtek] Verify & Identify entering state 1
164s (process:2449): libfprint-device-DEBUG: 05:02:55.606: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.606: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.606: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.606: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.606: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.606: [realtek] Verify & Identify entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.606: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.606: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.606: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.607: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.607: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.607: [realtek] Verify & Identify entering state 3
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.607: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.607: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.607: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.607: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.608: Device reported finger status change: FP_FINGER_STATUS_NONE
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.608: [realtek] Verify & Identify entering state 4
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.608: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.608: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.608: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.608: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-device-DEBUG: 05:02:55.608: Device reported identify result
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.608: [realtek] Verify & Identify completed successfully
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.608: Verify complete!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.608: Device reported identify completion
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.608: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-device-DEBUG: 05:02:55.609: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.609: Not updating temperature model, device can run continuously!
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.609: 42357896: ../libfprint/drivers/realtek/realtek.c:1313
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.609: [realtek] Delete print entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.609: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.609: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.609: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.610: [realtek] Delete print entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.610: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.610: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.610: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.610: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.610: [realtek] Delete print completed successfully
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.610: Delete print complete!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.610: Device reported deletion completion
164s (process:2449): libfprint-SSM-DEBUG: 05:02:55.610: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
164s (process:2449): libfprint-device-DEBUG: 05:02:55.610: Completing action FPI_DEVICE_ACTION_DELETE in idle!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.610: Not updating temperature model, device can run continuously!
164s (process:2449): libfprint-realtek-DEBUG: 05:02:55.610: 42359294: ../libfprint/drivers/realtek/realtek.c:1301
164s (process:2449): libfprint-device-DEBUG: 05:02:55.610: Device reported close completion
164s (process:2449): libfprint-device-DEBUG: 05:02:55.610: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s (process:2449): libfprint-device-DEBUG: 05:02:55.611: Not updating temperature model, device can run continuously!
164s enrolling
164s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9820a340 (FpiDeviceRealtek at 0x2487b50)>, 1, None, None, None)
164s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9820a340 (FpiDeviceRealtek at 0x2487b50)>, 2, None, None, None)
164s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9820a340 (FpiDeviceRealtek at 0x2487b50)>, 3, None, None, None)
164s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9820a340 (FpiDeviceRealtek at 0x2487b50)>, 4, None, None, None)
164s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9820a340 (FpiDeviceRealtek at 0x2487b50)>, 5, None, None, None)
164s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9820a340 (FpiDeviceRealtek at 0x2487b50)>, 6, None, None, None)
164s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9820a340 (FpiDeviceRealtek at 0x2487b50)>, 7, None, None, None)
164s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ff9820a340 (FpiDeviceRealtek at 0x2487b50)>, 8, None, None, None)
164s enroll done
164s listing
164s listing done
164s verifying
164s verify done
164s async identifying
164s indentification_done:  <FPrint.Print object at 0x3ff98211b40 (FpPrint at 0x2485960)> <FPrint.Print object at 0x3ff98211b80 (FpPrint at 0x248d2b0)>
164s deleting
164s delete done
164s ** (umockdev-run:2445): DEBUG: 05:02:55.622: umockdev.vala:154: Removing test bed /tmp/umockdev.UT7J22
164s (umockdev-run:2445): GLib-DEBUG: 05:02:55.624: unsetenv() is not thread-safe and should not be used after threads are created
164s PASS: libfprint-2/driver-realtek.test
164s Running test: libfprint-2/driver-elanmoc.test
164s ** (umockdev-run:2457): DEBUG: 05:02:55.660: umockdev.vala:127: Created udev test bed /tmp/umockdev.WUB412
164s ** (umockdev-run:2457): DEBUG: 05:02:55.660: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9
164s ** (umockdev-run:2457): DEBUG: 05:02:55.662: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb)
164s ** (umockdev-run:2457): DEBUG: 05:02:55.663: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WUB412/dev/bus/usb/001/003
164s ** (umockdev-run:2457): DEBUG: 05:02:55.663: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
164s ** (umockdev-run:2457): DEBUG: 05:02:55.664: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
164s ** (umockdev-run:2457): DEBUG: 05:02:55.665: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WUB412/dev/bus/usb/001/001
164s ** (umockdev-run:2457): DEBUG: 05:02:55.665: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0
164s ** (umockdev-run:2457): DEBUG: 05:02:55.665: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
164s (process:2461): libfprint-context-DEBUG: 05:02:55.724: Initializing FpContext (libfprint version 1.94.9+tod1)
164s (process:2461): libfprint-tod-DEBUG: 05:02:55.724: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.725: 42473765: ../libfprint/drivers/elanmoc/elanmoc.c:1154
164s (process:2461): libfprint-context-DEBUG: 05:02:55.725: No driver found for USB device 1D6B:0002
164s (process:2461): libfprint-device-DEBUG: 05:02:55.725: Device reported probe completion
164s (process:2461): libfprint-device-DEBUG: 05:02:55.725: Completing action FPI_DEVICE_ACTION_PROBE in idle!
164s (process:2461): libfprint-device-DEBUG: 05:02:55.725: Not updating temperature model, device can run continuously!
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.726: [elanmoc] DEV_INIT_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.726: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.726: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.726: [elanmoc] DEV_INIT_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.726: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.726: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.726: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.727: [elanmoc] DEV_INIT_STATES entering state 2
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.727: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.727: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.727: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.727: elanmoc  FW Version 8004 
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.727: [elanmoc] DEV_INIT_STATES entering state 3
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.727: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.727: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.727: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.728: elanmoc last_read DIM 0x57(87) 0x6B(107)
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.728: [elanmoc] DEV_INIT_STATES entering state 4
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.728: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.728: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.728: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.728: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01)
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.728: [elanmoc] DEV_INIT_STATES completed successfully
164s (process:2461): libfprint-device-DEBUG: 05:02:55.728: Device reported open completion
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.728: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-device-DEBUG: 05:02:55.728: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s (process:2461): libfprint-device-DEBUG: 05:02:55.728: Not updating temperature model, device can run continuously!
164s (process:2461): libfprint-device-DEBUG: 05:02:55.729: Not updating temperature model, device can run continuously!
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.729: [elanmoc] MOC_ENROLL_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.729: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.729: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.729: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01)
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.729: [elanmoc] MOC_ENROLL_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.730: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.730: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.730: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.730: ##### Re-Enrollment Case! #####
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.730: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.730: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.731: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.731: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-device-DEBUG: 05:02:55.731: Device reported enroll progress, reported 1 of 9 have been completed
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.731: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.731: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.731: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.731: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-device-DEBUG: 05:02:55.731: Device reported enroll progress, reported 2 of 9 have been completed
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.731: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.731: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.732: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.732: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-device-DEBUG: 05:02:55.732: Device reported enroll progress, reported 3 of 9 have been completed
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.732: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.732: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.732: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.732: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-device-DEBUG: 05:02:55.733: Device reported enroll progress, reported 4 of 9 have been completed
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.733: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.733: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.733: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.733: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-device-DEBUG: 05:02:55.733: Device reported enroll progress, reported 5 of 9 have been completed
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.733: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.733: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.734: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.734: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-device-DEBUG: 05:02:55.734: Device reported enroll progress, reported 6 of 9 have been completed
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.734: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.734: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.734: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.734: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-device-DEBUG: 05:02:55.735: Device reported enroll progress, reported 7 of 9 have been completed
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.735: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.735: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.735: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.735: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-device-DEBUG: 05:02:55.735: Device reported enroll progress, reported 7 of 9 have been completed
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.735: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.735: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.736: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.736: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-device-DEBUG: 05:02:55.736: Device reported enroll progress, reported 8 of 9 have been completed
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.736: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.736: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.736: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.736: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-device-DEBUG: 05:02:55.737: Device reported enroll progress, reported 8 of 9 have been completed
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.737: [elanmoc] MOC_ENROLL_NUM_STATES entering state 2
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.737: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.737: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.737: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-device-DEBUG: 05:02:55.737: Device reported enroll progress, reported 9 of 9 have been completed
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.737: [elanmoc] MOC_ENROLL_NUM_STATES entering state 3
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.737: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.738: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.738: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.738: elanmoc_commit_cb success
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.738: Enrollment was successful!
164s (process:2461): libfprint-device-DEBUG: 05:02:55.738: Device reported enroll completion
164s (process:2461): libfprint-device-DEBUG: 05:02:55.738: Print for finger FP_FINGER_UNKNOWN enrolled
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.738: [elanmoc] MOC_ENROLL_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.738: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-device-DEBUG: 05:02:55.738: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
164s (process:2461): libfprint-device-DEBUG: 05:02:55.738: Not updating temperature model, device can run continuously!
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.738: [elanmoc] MOC_LIST_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.738: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.738: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.739: elanmoc Current enrolled fingers in the Chipset: 1 (0x40 0x01)
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.739: [elanmoc] MOC_LIST_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.739: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.739: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.739: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.739: [elanmoc] MOC_LIST_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.739: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.740: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.740: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.740: [elanmoc] MOC_LIST_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.740: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.740: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.740: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.741: [elanmoc] MOC_LIST_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.741: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.741: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.741: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.741: [elanmoc] MOC_LIST_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.741: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.741: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.741: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.742: [elanmoc] MOC_LIST_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.742: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.742: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.742: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.742: [elanmoc] MOC_LIST_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.742: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.742: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.742: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.743: [elanmoc] MOC_LIST_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.743: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.743: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.743: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.743: [elanmoc] MOC_LIST_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.743: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.743: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.743: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.744: [elanmoc] MOC_LIST_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.744: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.744: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.744: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-device-DEBUG: 05:02:55.744: Device reported listing completion
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.744: [elanmoc] MOC_LIST_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.744: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-device-DEBUG: 05:02:55.744: Completing action FPI_DEVICE_ACTION_LIST in idle!
164s (process:2461): libfprint-device-DEBUG: 05:02:55.744: Not updating temperature model, device can run continuously!
164s (process:2461): libfprint-device-DEBUG: 05:02:55.744: Not updating temperature model, device can run continuously!
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.744: [elanmoc] IDENTIFY_NUM_STATES entering state 0
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.744: elanmoc elan_identify_run_state 
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.744: elanmoc elan_identify_run_state IDENTIFY_SET_MODE
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.744: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.745: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.745: [elanmoc] IDENTIFY_NUM_STATES entering state 1
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.745: elanmoc elan_identify_run_state 
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.745: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.745: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.745: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.745: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.745: Verify was successful! for user: 0 mesg_code: 1 
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.745: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.745: [elanmoc] IDENTIFY_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.745: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.746: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.746: Verify/Identify successful for: FP1-00000000-0-00000000-nobody
164s (process:2461): libfprint-device-DEBUG: 05:02:55.746: Device reported verify result
164s (process:2461): libfprint-device-DEBUG: 05:02:55.746: Device reported verify completion
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.746: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-device-DEBUG: 05:02:55.746: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s (process:2461): libfprint-device-DEBUG: 05:02:55.746: Not updating temperature model, device can run continuously!
164s (process:2461): libfprint-device-DEBUG: 05:02:55.746: Not updating temperature model, device can run continuously!
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.746: [elanmoc] IDENTIFY_NUM_STATES entering state 0
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.746: elanmoc elan_identify_run_state 
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.746: elanmoc elan_identify_run_state IDENTIFY_SET_MODE
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.746: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.746: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.747: [elanmoc] IDENTIFY_NUM_STATES entering state 1
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.747: elanmoc elan_identify_run_state 
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.747: elanmoc elan_identify_run_state VERIFY_WAIT_FINGER
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.747: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.747: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.747: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.747: Verify was successful! for user: 0 mesg_code: 1 
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.747: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.747: [elanmoc] IDENTIFY_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.747: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.747: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.748: Verify/Identify successful for: FP1-00000000-0-00000000-nobody
164s (process:2461): libfprint-device-DEBUG: 05:02:55.748: Device reported identify result
164s (process:2461): libfprint-device-DEBUG: 05:02:55.748: Device reported identify completion
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.748: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-device-DEBUG: 05:02:55.748: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s (process:2461): libfprint-device-DEBUG: 05:02:55.748: Not updating temperature model, device can run continuously!
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.748: Delete Finger, user_id = FP1-00000000-0-00000000-nobody!
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.748: [elanmoc] DELETE_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.748: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.748: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-device-DEBUG: 05:02:55.749: Device reported deletion completion
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.749: [elanmoc] DELETE_NUM_STATES completed successfully
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.749: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-device-DEBUG: 05:02:55.749: Completing action FPI_DEVICE_ACTION_DELETE in idle!
164s (process:2461): libfprint-device-DEBUG: 05:02:55.749: Not updating temperature model, device can run continuously!
164s (process:2461): libfprint-elanmoc-DEBUG: 05:02:55.749: Elanmoc dev_exit
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.749: [elanmoc] DEV_EXIT_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.749: [elanmoc] FP_CMD_NUM_STATES entering state 0
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.749: [elanmoc] FP_CMD_NUM_STATES entering state 1
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.749: [elanmoc] DEV_EXIT_STATES completed successfully
164s (process:2461): libfprint-device-DEBUG: 05:02:55.749: Device reported close completion
164s (process:2461): libfprint-SSM-DEBUG: 05:02:55.749: [elanmoc] FP_CMD_NUM_STATES completed successfully
164s (process:2461): libfprint-device-DEBUG: 05:02:55.749: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s (process:2461): libfprint-device-DEBUG: 05:02:55.749: Not updating temperature model, device can run continuously!
164s enrolling
164s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff8dad0300 (FpiDeviceElanmoc at 0x39611a0)>, 1, None, None, None)
164s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff8dad0300 (FpiDeviceElanmoc at 0x39611a0)>, 2, None, None, None)
164s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff8dad0300 (FpiDeviceElanmoc at 0x39611a0)>, 3, None, None, None)
164s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff8dad0300 (FpiDeviceElanmoc at 0x39611a0)>, 4, None, None, None)
164s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff8dad0300 (FpiDeviceElanmoc at 0x39611a0)>, 5, None, None, None)
164s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff8dad0300 (FpiDeviceElanmoc at 0x39611a0)>, 6, None, None, None)
164s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff8dad0300 (FpiDeviceElanmoc at 0x39611a0)>, 7, None, None, None)
164s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff8dad0300 (FpiDeviceElanmoc at 0x39611a0)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
164s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff8dad0300 (FpiDeviceElanmoc at 0x39611a0)>, 8, None, None, None)
164s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff8dad0300 (FpiDeviceElanmoc at 0x39611a0)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
164s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
164s enroll progress: (<__gi__.FpiDeviceElanmoc object at 0x3ff8dad0300 (FpiDeviceElanmoc at 0x39611a0)>, 9, None, None, None)
164s enroll done
164s listing
164s listing done
164s verifying
164s verify done
164s async identifying
164s indentification_done:  <FPrint.Print object at 0x3ff8d20d7c0 (FpPrint at 0x3973800)> <FPrint.Print object at 0x3ff8d20d800 (FpPrint at 0x3976a30)>
164s deleting
164s delete done
164s ** (umockdev-run:2457): DEBUG: 05:02:55.759: umockdev.vala:154: Removing test bed /tmp/umockdev.WUB412
164s (umockdev-run:2457): GLib-DEBUG: 05:02:55.761: unsetenv() is not thread-safe and should not be used after threads are created
164s PASS: libfprint-2/driver-elanmoc.test
164s Running test: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test
164s TAP version 14
164s # random seed: R02S5ce5c3ab9673baf677f17e40b6d06e18
164s 1..97
164s # Start of driver tests
164s ok 1 /driver/get_driver
164s ok 2 /driver/get_device_id
164s ok 3 /driver/get_name
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 4 /driver/is_open
164s ok 5 /driver/get_nr_enroll_stages
164s ok 6 /driver/set_nr_enroll_stages
164s ok 7 /driver/supports_identify
164s ok 8 /driver/supports_capture
164s ok 9 /driver/has_storage
164s ok 10 /driver/do_not_support_identify
164s ok 11 /driver/do_not_support_capture
164s ok 12 /driver/has_not_storage
164s ok 13 /driver/get_usb_device
164s ok 14 /driver/get_virtual_env
164s ok 15 /driver/get_driver_data
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
164s # 
164s # libfprint-device-DEBUG: Device reported probe completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s ok 16 /driver/initial_features
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE
164s # 
164s # libfprint-device-DEBUG: Device reported probe completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 17 /driver/probe
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 18 /driver/open
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 19 /driver/close
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
164s # 
164s # libfprint-device-DEBUG: Device reported enroll completion
164s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 20 /driver/enroll
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
164s # 
164s # libfprint-device-DEBUG: Device reported verify result
164s # libfprint-device-DEBUG: Device reported verify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 21 /driver/verify
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
164s # 
164s # libfprint-device-DEBUG: Device reported identify result
164s # libfprint-device-DEBUG: Device reported identify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 22 /driver/identify
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
164s # 
164s # libfprint-device-DEBUG: Device reported capture completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 23 /driver/capture
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
164s # 
164s # libfprint-device-DEBUG: Device reported listing completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 24 /driver/list
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
164s # 
164s # libfprint-device-DEBUG: Device reported deletion completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 25 /driver/delete
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
164s # 
164s # libfprint-device-DEBUG: Device reported deletion completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 26 /driver/clear_storage
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Idle cancelling on ongoing operation!
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
164s # 
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
164s # 
164s # libfprint-device-DEBUG: Device reported deletion completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 27 /driver/cancel
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Idle cancelling on ongoing operation!
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
164s # 
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
164s # 
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
164s # 
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
164s # 
164s # libfprint-device-DEBUG: Device reported verify result
164s # libfprint-device-DEBUG: Device reported verify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 28 /driver/critical
164s ok 29 /driver/get_current_action
164s ok 30 /driver/timeout
164s ok 31 /driver/error_types
164s ok 32 /driver/retry_error_types
164s # Start of get_scan_type tests
164s ok 33 /driver/get_scan_type/press
164s ok 34 /driver/get_scan_type/swipe
164s # End of get_scan_type tests
164s # Start of set_scan_type tests
164s ok 35 /driver/set_scan_type/press
164s ok 36 /driver/set_scan_type/swipe
164s # End of set_scan_type tests
164s # Start of finger_status tests
164s ok 37 /driver/finger_status/inactive
164s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s ok 38 /driver/finger_status/waiting
164s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s ok 39 /driver/finger_status/present
164s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED
164s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
164s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT
164s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE
164s ok 40 /driver/finger_status/changes
164s # End of finger_status tests
164s # Start of features tests
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
164s # 
164s # libfprint-device-DEBUG: Device reported probe completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 41 /driver/features/probe_updates
164s # End of features tests
164s # Start of initial_features tests
164s ok 42 /driver/initial_features/none
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s ok 43 /driver/initial_features/no_capture
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s ok 44 /driver/initial_features/no_verify
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s ok 45 /driver/initial_features/no_identify
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s ok 46 /driver/initial_features/no_storage
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s ok 47 /driver/initial_features/no_list
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s ok 48 /driver/initial_features/no_delete
164s ok 49 /driver/initial_features/no_clear
164s # End of initial_features tests
164s # Start of probe tests
164s # libfprint-device-DEBUG: Device reported probe completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 50 /driver/probe/error
164s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE
164s # libfprint-device-DEBUG: Device reported probe completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 51 /driver/probe/action_error
164s # End of probe tests
164s # Start of open tests
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 52 /driver/open/error
164s # End of open tests
164s # Start of close tests
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 53 /driver/close/error
164s # End of close tests
164s # Start of enroll tests
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
164s # 
164s # libfprint-device-DEBUG: Device reported enroll completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 54 /driver/enroll/error
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Device reported enroll progress, reported 1554527737 of 1515555007 have been completed
164s # libfprint-device-DEBUG: Device reported enroll progress, reported 2006753478 of 1515555007 have been completed
164s # libfprint-device-DEBUG: Device reported enroll progress, reported 1659388438 of 1515555007 have been completed
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
164s # 
164s # libfprint-device-DEBUG: Device reported enroll completion
164s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 55 /driver/enroll/progress
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
164s # 
164s # libfprint-device-DEBUG: Device reported enroll completion
164s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 56 /driver/enroll/update_nbis
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 57 /driver/enroll/update_nbis_wrong_device
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 58 /driver/enroll/update_nbis_wrong_driver
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 59 /driver/enroll/update_nbis_missing_feature
164s # Start of error tests
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Device reported enroll completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s # libfprint-device-DEBUG: Device reported enroll completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s # libfprint-device-DEBUG: Device reported enroll completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 60 /driver/enroll/error/no_print
164s # End of error tests
164s # End of enroll tests
164s # Start of verify tests
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
164s # 
164s # libfprint-device-DEBUG: Device reported verify result
164s # libfprint-device-DEBUG: Device reported verify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 61 /driver/verify/fail
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
164s # 
164s # libfprint-device-DEBUG: Device reported verify result
164s # libfprint-device-DEBUG: Device reported verify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 62 /driver/verify/retry
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
164s # 
164s # libfprint-device-DEBUG: Device reported verify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 63 /driver/verify/error
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 64 /driver/verify/not_supported
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Device reported verify result
164s # libfprint-device-DEBUG: Device reported verify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 65 /driver/verify/report_no_cb
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Device reported verify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 66 /driver/verify/not_reported
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Device reported verify result
164s # libfprint-device-DEBUG: Device reported verify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s # libfprint-device-DEBUG: Device reported verify result
164s # libfprint-device-DEBUG: Device reported verify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s # libfprint-device-DEBUG: Device reported verify result
164s # libfprint-device-DEBUG: Device reported verify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s # libfprint-device-DEBUG: Device reported verify result
164s # libfprint-device-DEBUG: Device reported verify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s # libfprint-device-DEBUG: Device reported verify result
164s # libfprint-device-DEBUG: Device reported verify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 67 /driver/verify/complete_retry
164s # End of verify tests
164s # Start of identify tests
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
164s # 
164s # libfprint-device-DEBUG: Device reported identify result
164s # libfprint-device-DEBUG: Device reported identify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD
164s ok 68 /driver/identify/fail
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
164s # 
164s # libfprint-device-DEBUG: Device reported identify result
164s # libfprint-device-DEBUG: Device reported identify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 69 /driver/identify/retry
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
164s # 
164s # libfprint-device-DEBUG: Device reported identify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 70 /driver/identify/error
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Device reported identify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 71 /driver/identify/not_reported
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Device reported identify result
164s # libfprint-device-DEBUG: Device reported identify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Device reported identify result
164s # libfprint-device-DEBUG: Device reported identify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s # libfprint-device-DEBUG: Device reported identify result
164s # libfprint-device-DEBUG: Device reported identify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 72 /driver/identify/complete_retry
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Device reported identify result
164s # libfprint-device-DEBUG: Device reported identify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 73 /driver/identify/report_no_cb
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
164s # 
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
164s # 
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
164s # 
164s # libfprint-device-DEBUG: Device reported identify result
164s # libfprint-device-DEBUG: Device reported identify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 74 /driver/identify/suspend_continues
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
164s # 
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
164s # 
164s # libfprint-device-DEBUG: Device reported identify result
164s # libfprint-device-DEBUG: Device reported identify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 75 /driver/identify/suspend_succeeds
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
164s # 
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
164s # 
164s # libfprint-device-DEBUG: Device reported identify completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
164s ok 76 /driver/identify/suspend_busy_error
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
164s # 
164s # libfprint-device-DEBUG: Device reported close completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s ok 77 /driver/identify/suspend_while_idle
164s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
164s # libfprint-device-DEBUG: Tod version info is 'current'
164s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
164s # 
164s # libfprint-device-DEBUG: Device reported open completion
164s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
164s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
165s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
167s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT
167s # libfprint-device-DEBUG: Idle cancelling on ongoing operation!
167s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
167s # 
167s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
167s # 
167s # libfprint-device-DEBUG: Device reported identify completion
167s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
167s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT
167s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT
167s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT
168s Executing: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test
169s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM
172s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s ok 78 /driver/identify/warmup_cooldown
172s # slow test /driver/identify/warmup_cooldown executed in 7.29 secs
172s # End of identify tests
172s # Start of capture tests
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
172s # 
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s ok 79 /driver/capture/not_supported
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
172s # 
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
172s # 
172s # libfprint-device-DEBUG: Device reported capture completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s ok 80 /driver/capture/error
172s # End of capture tests
172s # Start of list tests
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
172s # 
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
172s # 
172s # libfprint-device-DEBUG: Device reported listing completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s ok 81 /driver/list/error
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
172s # 
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s ok 82 /driver/list/no_storage
172s # End of list tests
172s # Start of delete tests
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
172s # 
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
172s # 
172s # libfprint-device-DEBUG: Device reported deletion completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s ok 83 /driver/delete/error
172s # End of delete tests
172s # Start of clear_storage tests
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
172s # 
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
172s # libfprint-device-DEBUG: Tod version info is 'current'
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
172s # 
172s # libfprint-device-DEBUG: Device reported deletion completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s ok 84 /driver/clear_storage/error
172s # End of clear_storage tests
172s # Start of cancel tests
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
172s # 
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
172s # 
172s # libfprint-device-DEBUG: Device reported deletion completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s ok 85 /driver/cancel/fail
172s # End of cancel tests
172s # Start of get_current_action tests
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s ok 86 /driver/get_current_action/open
172s # End of get_current_action tests
172s # Start of get_cancellable tests
172s ok 87 /driver/get_cancellable/error
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s ok 88 /driver/get_cancellable/open
172s # Start of open tests
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s ok 89 /driver/get_cancellable/open/internal
172s # End of open tests
172s # End of get_cancellable tests
172s # Start of action_is_cancelled tests
172s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
172s # libfprint-device-DEBUG: Tod version info is 'current'
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s ok 90 /driver/action_is_cancelled/open
172s ok 91 /driver/action_is_cancelled/error
172s # Start of open tests
172s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
172s # libfprint-device-DEBUG: Tod version info is 'current'
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s ok 92 /driver/action_is_cancelled/open/internal
172s # End of open tests
172s # End of action_is_cancelled tests
172s # Start of complete_action tests
172s # Start of all tests
172s ok 93 /driver/complete_action/all/error
172s # End of all tests
172s # End of complete_action tests
172s # Start of action_error tests
172s ok 94 /driver/action_error/error
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
172s # 
172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
172s # 
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
172s # 
172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL
172s # libfprint-device-DEBUG: Device reported enroll completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
172s # 
172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY
172s # libfprint-device-DEBUG: Device reported verify completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
172s # 
172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY
172s # libfprint-device-DEBUG: Device reported identify completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
172s # 
172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE
172s # libfprint-device-DEBUG: Device reported capture completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
172s # 
172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST
172s # libfprint-device-DEBUG: Device reported listing completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
172s # 
172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE
172s # libfprint-device-DEBUG: Device reported deletion completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
172s # libfprint-device-DEBUG: Tod version info is 'current'
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
172s # 
172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE
172s # libfprint-device-DEBUG: Device reported deletion completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s ok 95 /driver/action_error/all
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
172s # 
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
172s # 
172s # libfprint-device-DEBUG: Device reported open completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
172s # 
172s # libfprint-device-DEBUG: Device reported enroll completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
172s # 
172s # libfprint-device-DEBUG: Device reported verify completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
172s # 
172s # libfprint-device-DEBUG: Device reported identify completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
172s # 
172s # libfprint-device-DEBUG: Device reported capture completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
172s # 
172s # libfprint-device-DEBUG: Device reported listing completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
172s # 
172s # libfprint-device-DEBUG: Device reported deletion completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-device-DEBUG: Getting TOD version for driver 'fake_test_dev_tod_current'
172s # libfprint-device-DEBUG: Tod version info is 'current'
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
172s # 
172s # libfprint-device-DEBUG: Device reported deletion completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
172s # 
172s # libfprint-device-DEBUG: Device reported close completion
172s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
172s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
172s ok 96 /driver/action_error/fail
172s # End of action_error tests
172s # Start of timeout tests
172s ok 97 /driver/timeout/cancelled
172s # End of timeout tests
172s # End of driver tests
172s PASS: libfprint-2/tod-fpi-device-tod-fake_test_dev_tod_current.test
172s Running test: libfprint-2/driver-vfs7552.test
172s ** (umockdev-run:2475): DEBUG: 05:03:03.302: umockdev.vala:127: Created udev test bed /tmp/umockdev.0ZZI22
172s ** (umockdev-run:2475): DEBUG: 05:03:03.302: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7
172s ** (umockdev-run:2475): DEBUG: 05:03:03.303: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb)
172s ** (umockdev-run:2475): DEBUG: 05:03:03.305: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.0ZZI22/dev/bus/usb/001/003
172s ** (umockdev-run:2475): DEBUG: 05:03:03.305: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
172s ** (umockdev-run:2475): DEBUG: 05:03:03.306: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
172s ** (umockdev-run:2475): DEBUG: 05:03:03.308: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.0ZZI22/dev/bus/usb/001/001
172s ** (umockdev-run:2475): DEBUG: 05:03:03.308: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0
172s ** (umockdev-run:2475): DEBUG: 05:03:03.308: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
172s (umockdev-run:2475): GLib-GIO-DEBUG: 05:03:03.310: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
172s (process:2479): libfprint-context-DEBUG: 05:03:03.385: Initializing FpContext (libfprint version 1.94.9+tod1)
172s (process:2479): libfprint-tod-DEBUG: 05:03:03.386: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
172s (process:2479): libfprint-context-DEBUG: 05:03:03.387: No driver found for USB device 1D6B:0002
172s (process:2479): libfprint-device-DEBUG: 05:03:03.387: Device reported probe completion
172s (process:2479): libfprint-device-DEBUG: 05:03:03.387: Completing action FPI_DEVICE_ACTION_PROBE in idle!
172s (process:2479): libfprint-device-DEBUG: 05:03:03.387: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.388: [vfs7552] DEV_OPEN_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.388: [vfs7552] DEVICE OPEN entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.388: Sending vfs7552_cmd_01
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.389: [vfs7552] DEVICE OPEN entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.389: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.389: Got 38 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.389: [vfs7552] DEVICE OPEN entering state 2
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.389: Sending vfs7552_cmd_19
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.389: [vfs7552] DEVICE OPEN entering state 3
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.389: Receiving 128 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.390: Got 68 bytes out of 128
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.390: [vfs7552] DEVICE OPEN entering state 4
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.390: Sending vfs7552_init_00
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.390: [vfs7552] DEVICE OPEN entering state 5
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.390: Receiving 64 bytes
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.390: [vfs7552] DEVICE OPEN entering state 6
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.390: Sending vfs7552_init_01
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.391: [vfs7552] DEVICE OPEN entering state 7
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.391: Receiving 64 bytes
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.391: [vfs7552] DEVICE OPEN entering state 8
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.391: Sending vfs7552_init_02
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.391: [vfs7552] DEVICE OPEN entering state 9
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.391: Receiving 64 bytes
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.392: [vfs7552] DEVICE OPEN entering state 10
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.392: Sending vfs7552_init_03
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.392: [vfs7552] DEVICE OPEN entering state 11
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.392: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.392: Got 10 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.392: [vfs7552] DEVICE OPEN entering state 12
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.392: Sending vfs7552_init_04
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.393: [vfs7552] DEVICE OPEN entering state 13
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.393: Receiving 64 bytes
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.393: [vfs7552] DEVICE OPEN completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.393: [vfs7552] DEV_OPEN_NUM_STATES completed successfully
172s (process:2479): libfprint-image_device-DEBUG: 05:03:03.393: Image device open completed
172s (process:2479): libfprint-device-DEBUG: 05:03:03.393: Device reported open completion
172s (process:2479): libfprint-device-DEBUG: 05:03:03.393: Completing action FPI_DEVICE_ACTION_OPEN in idle!
172s (process:2479): libfprint-device-DEBUG: 05:03:03.393: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s (process:2479): libfprint-device-DEBUG: 05:03:03.393: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
172s (process:2479): libfprint-image_device-DEBUG: 05:03:03.393: Activating image device
172s (process:2479): libfprint-image_device-DEBUG: 05:03:03.393: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
172s (process:2479): libfprint-image_device-DEBUG: 05:03:03.393: Image device activation completed
172s (process:2479): libfprint-image_device-DEBUG: 05:03:03.393: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
172s (process:2479): libfprint-image_device-DEBUG: 05:03:03.393: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
172s (process:2479): libfprint-device-DEBUG: 05:03:03.393: Device reported finger status change: FP_FINGER_STATUS_NEEDED
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.443: changing to 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.443: [vfs7552] ACTIVATE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.443: [vfs7552] ACTIVATE INIT entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.443: Sending vfs7552_image_start
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.444: [vfs7552] ACTIVATE INIT entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.444: Receiving 2048 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.444: Got 1962 bytes out of 2048
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.444: [vfs7552] ACTIVATE INIT completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.444: [vfs7552] ACTIVATE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.444: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.444: Receiving 8 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.445: Got 5 bytes out of 8
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.445: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.445: [vfs7552] ACTIVATE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.445: [vfs7552] ACTIVATE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.445: [vfs7552] ACTIVATE INTERRUPT QUERY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.445: Receiving 8 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.445: Got 5 bytes out of 8
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.445: [vfs7552] ACTIVATE INTERRUPT QUERY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.445: [vfs7552] ACTIVATE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.445: [vfs7552] ACTIVATE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.445: [vfs7552] ACTIVATE_NUM_STATES completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.445: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.445: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.445: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.445: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.445: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.445: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.446: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.446: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.446: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.446: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.446: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.446: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.446: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.446: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.446: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.446: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.446: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.446: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.446: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.446: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.446: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.447: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.447: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.447: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.447: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.447: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.447: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.447: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.447: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.447: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.447: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.447: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.447: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.447: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.447: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.448: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.448: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.448: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.448: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.448: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.448: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.448: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.448: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.448: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.448: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.448: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.448: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.448: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.448: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.448: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.448: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.449: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.449: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.449: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.449: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.449: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.449: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.449: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.449: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.449: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.449: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.450: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.450: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.450: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.450: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.450: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.450: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.450: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.450: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.450: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.450: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.450: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.450: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.450: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.450: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.451: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.451: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.451: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.451: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.451: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.451: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.451: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.451: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.451: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.451: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.451: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.451: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.451: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.451: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.451: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.451: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.452: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.452: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.452: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.452: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.452: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.452: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.452: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.452: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.453: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.453: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.453: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.453: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.453: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.453: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.453: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.453: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.453: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.453: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.454: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.454: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.454: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.454: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.454: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.454: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.454: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.454: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.454: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.454: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.454: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.454: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.454: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.454: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.455: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.455: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.455: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.455: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.455: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.455: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.455: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.455: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.455: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.455: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.456: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.456: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.456: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.456: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.456: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.456: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.456: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.456: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.456: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.456: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.456: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.456: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.456: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.456: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.457: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.457: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.457: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.457: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.457: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.457: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.457: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.457: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.457: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.457: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.458: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.458: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.458: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.458: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.458: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.458: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.458: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.458: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.458: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.458: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.459: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.459: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.459: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.459: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.459: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.459: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.459: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.459: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.459: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.459: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.459: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.459: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.460: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.460: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.460: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.460: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.460: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.460: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.460: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.460: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.460: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.460: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.461: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.461: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.461: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.461: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.461: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.461: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.461: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.461: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.461: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.461: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.461: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.461: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.461: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.461: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.462: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.462: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.462: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.462: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.462: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.462: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.462: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.462: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.462: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.462: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.463: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.463: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.463: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.463: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.463: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.463: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.463: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.463: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.463: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.463: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.463: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.463: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.463: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.463: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.463: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.463: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.464: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.464: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.464: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.464: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.464: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.464: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.464: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.464: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.464: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.464: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.464: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.464: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.464: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.464: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.464: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.464: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.465: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.465: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.465: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.465: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.465: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.465: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.465: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.465: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.465: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.465: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.465: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.465: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.465: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.465: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.466: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.466: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.466: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.466: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.466: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.466: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.466: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.466: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.466: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.466: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.467: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.467: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.467: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.467: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.467: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.467: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.467: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.467: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.467: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.467: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.467: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.467: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.467: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.467: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.468: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.468: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.468: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.468: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.468: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.468: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.468: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.468: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.468: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.468: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.469: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.469: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.469: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.469: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.469: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.469: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.469: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.469: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.469: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.469: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.469: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.469: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.469: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.469: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.470: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.470: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.470: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.470: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.470: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.470: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.470: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.470: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.470: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.470: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.471: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.471: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.471: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.471: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.471: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.471: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.471: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.471: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.472: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.472: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.472: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.472: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.472: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.472: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.472: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.472: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.472: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.472: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.472: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.472: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.472: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.472: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.473: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.473: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.473: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.473: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.473: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.473: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.473: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.473: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.473: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.473: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.473: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.473: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.473: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.473: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.473: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.473: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.474: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.474: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.474: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.474: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.474: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.474: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.474: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.474: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.474: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.474: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.475: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.475: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.475: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.475: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.475: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.475: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.475: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.475: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.475: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.475: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.475: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.475: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.475: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.475: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.476: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.476: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.476: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.476: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.476: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.476: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.476: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.476: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.476: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.476: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.477: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.477: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.477: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.477: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.477: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.477: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.477: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.477: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.477: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.477: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.477: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.477: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.477: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.477: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.478: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.478: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.478: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.478: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.478: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.478: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.478: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.478: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.478: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.478: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.479: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.479: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.479: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.479: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.479: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.479: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.479: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.479: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.479: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.479: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.479: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.479: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.479: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.479: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.480: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.480: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.480: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.480: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.480: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.480: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.480: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.480: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.480: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.480: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.480: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.480: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.480: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.480: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.480: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.480: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.481: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.481: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.481: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.481: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.481: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.481: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.481: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.481: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.481: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.481: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.482: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.482: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.482: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.482: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.482: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.482: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.482: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.482: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.482: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.482: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.482: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.482: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.482: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.482: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.483: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.483: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.483: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.483: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.483: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.483: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.483: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.483: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.483: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.483: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.484: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.484: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.484: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.484: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.484: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.484: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.484: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.484: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.484: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.484: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.484: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.484: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.484: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.484: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.485: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.485: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.485: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.485: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.485: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.485: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.485: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.485: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.485: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.485: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.485: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.486: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.486: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.486: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.486: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.486: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.486: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.486: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.486: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.486: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.486: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.486: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.486: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.486: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.486: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.486: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.487: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.487: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.487: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.487: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.487: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.487: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.487: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.487: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.487: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.487: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.487: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.487: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.487: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.487: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.488: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.488: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.488: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.488: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.488: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.488: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.488: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.488: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.488: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.488: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.489: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.489: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.489: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.489: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.489: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.489: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.489: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.489: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.489: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.489: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.489: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.489: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.489: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.489: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.490: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.490: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.490: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.490: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.490: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.490: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.490: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.490: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.490: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.490: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.491: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.491: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.491: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.491: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.491: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.491: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.491: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.491: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.491: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.491: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.491: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.491: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.491: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.491: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.492: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.492: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.492: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.492: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.492: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.492: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.492: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.492: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.492: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.492: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.493: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.493: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.493: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.493: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.493: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.493: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.493: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.493: Receiving 64 bytes
172s (process:2479): libfprint-device-DEBUG: 05:03:03.493: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.493: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.493: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.493: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.493: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.493: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.493: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.494: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.494: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.494: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.494: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.494: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.494: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.494: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.494: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.494: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.494: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.495: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.495: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.495: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.495: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.495: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.495: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.495: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.495: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.495: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.495: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.495: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.495: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.495: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.495: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.495: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.495: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.496: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.496: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.496: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.496: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.496: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.496: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.496: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.496: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.496: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.496: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.496: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.496: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.496: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.496: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.497: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.497: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.497: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.497: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.497: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.497: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.497: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.497: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.497: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.497: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.498: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.498: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.498: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.498: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.498: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.498: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.498: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.498: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.498: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.498: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.498: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.498: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.498: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.498: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.499: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.499: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.499: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.499: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.499: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.499: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.499: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.499: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.499: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.499: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.500: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.500: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.500: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.500: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.500: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.500: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.500: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.500: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.500: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.500: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.500: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.500: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.500: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.500: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.501: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.501: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.501: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.501: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.501: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.501: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.501: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.501: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.501: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.501: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.502: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.502: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.502: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.502: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.502: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.502: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.502: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.502: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.502: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.502: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.502: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.502: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.502: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.502: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.503: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.503: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.503: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.503: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.503: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.503: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.503: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.503: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.503: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.503: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.504: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.504: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.504: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.504: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.504: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.504: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.504: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.504: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.504: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.504: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.504: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.505: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.505: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.505: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.505: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.505: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.506: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.506: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.506: [vfs7552] CAPTURE_NUM_STATES entering state 4
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.506: variance_before = 396
172s 
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.506: background stored
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.506: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.506: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.506: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.506: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.506: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.507: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.507: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.507: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.507: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.507: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.507: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.507: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.507: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.507: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.507: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.507: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.507: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.507: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.507: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.508: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.508: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.508: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.508: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.508: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.508: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.508: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.508: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.508: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.508: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.509: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.509: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.509: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.509: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.509: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.509: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.509: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.509: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.509: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.509: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.509: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.509: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.509: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.509: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.510: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.510: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.510: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.510: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.510: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.510: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.510: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.510: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.511: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.511: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.511: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.511: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.511: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.511: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.511: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.511: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.511: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.511: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.512: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.512: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.512: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.512: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.512: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.512: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.512: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.512: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.512: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.512: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.512: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.512: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.512: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.512: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.513: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.513: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.513: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.513: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.513: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.513: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.513: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.513: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.513: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.513: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.514: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.514: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.514: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.514: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.514: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.514: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.514: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.514: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.514: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.514: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.514: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.514: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.514: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.514: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.515: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.515: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.515: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.515: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.515: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.515: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.515: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.515: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.515: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.515: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.516: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.516: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.516: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.516: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.516: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.516: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.516: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.516: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.516: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.516: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.516: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.516: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.516: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.516: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.517: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.517: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.517: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.517: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.517: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.517: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.517: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.517: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.517: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.517: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.517: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.517: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.517: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.517: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.517: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.517: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.518: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.518: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.518: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.518: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.518: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.518: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.518: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.518: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.519: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.519: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.519: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.519: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.519: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.519: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.519: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.519: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.519: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.519: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.520: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.520: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.520: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.520: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.520: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.520: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.520: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.520: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.520: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.520: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.520: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.520: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.520: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.520: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.521: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.521: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.521: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.521: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.521: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.521: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.521: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.521: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.521: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.521: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.522: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.522: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.522: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.522: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.522: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.522: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.522: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.522: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.522: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.522: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.522: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.522: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.522: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.522: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.523: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.523: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.523: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.523: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.523: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.523: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.523: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.523: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.523: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.523: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.524: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.524: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.524: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.524: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.524: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.524: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.524: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.524: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.524: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.524: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.524: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.524: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.524: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.524: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.525: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.525: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.525: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.525: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.525: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.525: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.525: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.525: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.525: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.525: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.526: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.526: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.526: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.526: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.526: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.526: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.526: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.526: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.526: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.526: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.526: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.526: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.526: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.526: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.527: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.527: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.527: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.527: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.527: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.527: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.527: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.527: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.527: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.527: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.528: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.528: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.528: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.528: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.528: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.528: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.528: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.528: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.528: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.529: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.529: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.529: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.529: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.529: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.529: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.529: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.529: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.529: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.529: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.529: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.529: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.529: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.530: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.530: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.530: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.530: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.530: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.530: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.530: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.530: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.530: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.530: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.530: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.530: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.530: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.530: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.530: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.530: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.531: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.531: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.531: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.531: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.531: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.531: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.531: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.531: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.531: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.531: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.532: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.532: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.532: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.532: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.532: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.532: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.532: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.532: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.532: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.532: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.532: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.532: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.532: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.532: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.533: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.533: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.533: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.533: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.533: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.533: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.533: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.533: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.534: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.534: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.534: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.534: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.534: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.534: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.534: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.534: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.534: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.534: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.535: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.535: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.535: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.535: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.535: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.535: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.535: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.535: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.535: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.535: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.535: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.535: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.535: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.535: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.535: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.535: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.536: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.536: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.536: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.536: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.536: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.536: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.536: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.536: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.536: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.536: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.536: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.536: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.536: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.536: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.537: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.537: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.537: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.537: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.537: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.537: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.537: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.537: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.537: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.537: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.538: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.538: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.538: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.538: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.538: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.538: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.538: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.538: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.538: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.538: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.538: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.538: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.538: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.538: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.539: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.539: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.539: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.539: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.539: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.539: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.539: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.539: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.539: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.539: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.540: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.540: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.540: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.540: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.540: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.540: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.540: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.540: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.540: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.540: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.540: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.540: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.540: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.540: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.540: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.541: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.541: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.541: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.541: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.541: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.541: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.541: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.541: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.541: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.542: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.542: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.542: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.542: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.542: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.542: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.542: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.542: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.542: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.542: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.542: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.542: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.542: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.542: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.542: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.542: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.543: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.543: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.543: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.543: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.543: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.543: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.543: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.543: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.543: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.543: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.543: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.543: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.543: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.543: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.544: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.544: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.544: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.544: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.544: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.544: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.544: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.544: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.544: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.544: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.545: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.545: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.545: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.545: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.545: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.545: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.545: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.545: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.545: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.545: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.545: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.545: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.545: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.545: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.546: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.546: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.546: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.546: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.546: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.546: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.546: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.546: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.546: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.546: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.547: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.547: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.547: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.547: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.547: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.547: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.547: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.547: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.547: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.547: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.547: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.547: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.547: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.547: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.548: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.548: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.548: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.548: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.548: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.548: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.548: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.548: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.548: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.548: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.549: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.549: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.549: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.549: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.549: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.549: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.549: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.549: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.549: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.549: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.549: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.549: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.549: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.549: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.550: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.550: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.550: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.550: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.550: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.550: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.550: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.550: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.550: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.550: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.551: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.551: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.551: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.551: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.551: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.551: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.551: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.551: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.551: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.551: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.551: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.551: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.551: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.551: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.551: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.551: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.552: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.552: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.552: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.552: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.552: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.552: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.552: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.552: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.552: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.552: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.552: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.552: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.552: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.552: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.553: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.553: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.553: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.553: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.553: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.553: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.553: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.553: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.553: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.553: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.554: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.554: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.554: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.554: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.554: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.554: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.554: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.554: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.554: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.554: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.554: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.554: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.554: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.554: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.555: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.555: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.555: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.555: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.555: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.555: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.555: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.555: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.555: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.555: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.556: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.556: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.556: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.556: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.556: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.556: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.556: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.556: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.556: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.556: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.556: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.556: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.556: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.556: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.557: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.557: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.557: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.557: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.557: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.557: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.557: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.557: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.557: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.557: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.558: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.558: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.558: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.558: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.558: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.558: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.558: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.558: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.558: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.558: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.558: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.558: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.558: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.558: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.559: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.559: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.559: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.559: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.559: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.559: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.559: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.559: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.559: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.559: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.559: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.559: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.559: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.559: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.559: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.559: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.560: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.560: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.560: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.560: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.560: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.560: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.560: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.560: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.560: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.560: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.561: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.561: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.561: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.561: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.561: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.561: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.561: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.561: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.561: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.561: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.561: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.561: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.561: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.561: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.562: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.562: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.562: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.562: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.562: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.562: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.562: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.562: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.562: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.562: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.563: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.563: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.563: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.563: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.563: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.563: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.563: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.563: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.563: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.563: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.563: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.563: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.563: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.563: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.564: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.564: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.564: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.564: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.564: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.564: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.564: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.564: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.564: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.564: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.565: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.565: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.565: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.565: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.565: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.565: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.565: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.565: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.565: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.565: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.565: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.565: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.565: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.565: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.566: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.566: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.566: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.566: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.566: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.566: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.566: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.566: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.566: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.566: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.567: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.567: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.567: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.567: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.567: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.567: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.567: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.567: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.567: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.567: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.567: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.567: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.567: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.567: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.568: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.568: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.568: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.568: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.568: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.568: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.568: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.568: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.568: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.568: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.569: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.569: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.569: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.569: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.569: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.569: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.569: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.569: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.569: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.569: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.569: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.569: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.569: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.569: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.570: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.570: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.570: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.570: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.570: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.570: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.570: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.570: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.570: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.570: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.570: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.570: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.570: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.570: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.570: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.570: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.571: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.571: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.571: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.571: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.571: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.571: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.571: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.571: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.571: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.572: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.572: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.572: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.572: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.572: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.572: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.572: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.572: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.572: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.572: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.572: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.572: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.572: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.572: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.572: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.573: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.573: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.573: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.573: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.573: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.573: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.573: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.573: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.573: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.573: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.574: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.574: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.574: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.574: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.574: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.574: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.574: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.574: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.574: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.574: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.574: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.574: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.574: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.574: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.575: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.575: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.575: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.575: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.575: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.575: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.575: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.576: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.576: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.576: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.576: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.576: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.576: [vfs7552] CAPTURE_NUM_STATES entering state 4
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.576: Cleaning image
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.576: variance_after = 20
172s 
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.576: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.576: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.576: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.577: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.577: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.577: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.577: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.577: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.577: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.577: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.577: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.577: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.577: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.578: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.578: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.578: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.578: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.578: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.578: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.578: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.578: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.578: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.578: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.578: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.578: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.578: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.578: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.579: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.579: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.579: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.579: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.579: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.579: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.579: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.579: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.579: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.579: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.580: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.580: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.580: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.580: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.580: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.580: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.580: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.580: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.580: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.580: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.580: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.580: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.580: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.580: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.580: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.580: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.581: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.581: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.581: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.581: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.581: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.581: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.581: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.581: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.582: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.582: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.582: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.582: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.582: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.582: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.582: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.582: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.582: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.582: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.582: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.582: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.582: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.582: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.583: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.583: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.583: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.583: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.583: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.583: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.583: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.583: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.583: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.583: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.584: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.584: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.584: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.584: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.584: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.584: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.584: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.584: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.584: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.584: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.584: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.584: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.584: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.584: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.585: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.585: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.585: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.585: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.585: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.585: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.585: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.585: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.585: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.585: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.586: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.586: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.586: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.586: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.586: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.586: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.586: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.586: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.586: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.586: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.586: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.586: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.586: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.586: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.587: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.587: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.587: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.587: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.587: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.587: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.587: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.587: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.587: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.587: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.588: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.588: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.588: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.588: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.588: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.588: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.588: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.588: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.588: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.588: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.588: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.588: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.588: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.588: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.589: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.589: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.589: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.589: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.589: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.589: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.589: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.589: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.590: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.590: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.590: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.590: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.590: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.590: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.590: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.590: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.590: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.590: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.591: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.591: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.591: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.591: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.591: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.591: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.591: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.591: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.591: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.591: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.591: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.591: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.591: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.591: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.592: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.592: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.592: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.592: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.592: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.592: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.592: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.592: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.592: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.592: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.593: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.593: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.593: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.593: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.593: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.593: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.593: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.593: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.593: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.593: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.593: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.593: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.593: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.593: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.594: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.594: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.594: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.594: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.594: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.594: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.594: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.594: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.594: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.594: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.595: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.595: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.595: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.595: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.595: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.595: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.595: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.595: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.595: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.595: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.595: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.595: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.595: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.595: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.596: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.596: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.596: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.596: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.596: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.596: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.596: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.596: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.596: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.596: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.596: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.597: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.597: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.597: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.597: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.597: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.597: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.597: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.597: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.597: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.597: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.597: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.597: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.597: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.597: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.597: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.598: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.598: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.598: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.598: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.598: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.598: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.598: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.598: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.598: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.598: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.598: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.598: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.598: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.598: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.598: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.598: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.599: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.599: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.599: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.599: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.599: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.599: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.599: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.599: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.599: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.599: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.599: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.599: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.599: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.599: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.600: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.600: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.600: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.600: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.600: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.600: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.600: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.600: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.600: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.600: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.601: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.601: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.601: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.601: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.601: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.601: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.601: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.601: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.602: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.602: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.602: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.602: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.602: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.602: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.602: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.602: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.602: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.602: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.602: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.602: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.602: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.602: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.602: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.603: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.603: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.603: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.603: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.603: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.603: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.603: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.603: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.603: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.603: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.603: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.603: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.603: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.603: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.603: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.604: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.604: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.604: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.604: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.604: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.604: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.604: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.604: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.604: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.604: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.605: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.605: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.605: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.605: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.605: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.605: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.605: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.605: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.605: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.605: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.605: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.605: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.605: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.605: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.606: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.606: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.606: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.606: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.606: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.606: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.606: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.606: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.606: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.606: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.607: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.607: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.607: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.607: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.607: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.607: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.607: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.607: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.607: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.607: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.607: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.607: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.607: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.607: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.607: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.607: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.608: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.608: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.608: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.608: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.608: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.608: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.608: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.608: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.608: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.608: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.608: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.608: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.608: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.608: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.609: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.609: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.609: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.609: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.609: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.609: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.609: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.609: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.609: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.609: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.610: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.610: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.610: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.610: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.610: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.610: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.610: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.610: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.610: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.610: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.610: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.610: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.610: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.610: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.611: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.611: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.611: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.611: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.611: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.611: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.611: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.611: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.611: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.611: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.611: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.611: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.611: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.611: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.611: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.611: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.612: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.612: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.612: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.612: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.612: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.612: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.612: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.612: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.612: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.612: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.613: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.613: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.613: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.613: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.613: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.613: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.613: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.613: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.613: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.613: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.613: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.613: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.613: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.613: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.614: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.614: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.614: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.614: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.614: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.614: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.614: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.614: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.614: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.614: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.615: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.615: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.615: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.615: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.615: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.615: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.615: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.615: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.615: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.615: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.615: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.615: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.615: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.615: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.616: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.616: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.616: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.616: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.616: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.616: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.616: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.616: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.616: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.616: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.617: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.617: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.617: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.617: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.617: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.617: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.617: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.617: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.617: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.617: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.617: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.618: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.618: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.618: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.618: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.618: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.618: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.618: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.619: [vfs7552] CAPTURE_NUM_STATES entering state 4
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.619: Cleaning image
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.619: variance_after = 18
172s 
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.619: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.619: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.619: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.619: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.619: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.619: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.619: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.619: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.619: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.619: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.619: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.620: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.620: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.620: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.620: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.620: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.620: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.620: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.620: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.620: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.620: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.620: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.621: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.621: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.621: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.621: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.621: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.621: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.621: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.621: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.621: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.621: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.621: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.621: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.621: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.621: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.621: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.622: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.622: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.622: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.622: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.622: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.622: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.622: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.622: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.622: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.622: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.622: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.622: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.622: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.622: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.623: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.623: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.623: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.623: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.623: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.623: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.623: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.623: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.623: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.623: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.623: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.623: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.623: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.623: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.623: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.623: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.624: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.624: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.624: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.624: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.624: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.624: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.624: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.624: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.624: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.624: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.624: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.625: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.625: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.625: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.625: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.625: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.625: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.625: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.625: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.625: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.625: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.625: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.625: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.625: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.625: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.625: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.625: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.625: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.625: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.625: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.625: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.625: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.626: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.626: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.626: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.626: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.626: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.626: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.626: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.626: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.626: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.626: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.627: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.627: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.627: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.627: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.627: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.627: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.627: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.627: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.627: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.627: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.627: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.627: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.627: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.627: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.627: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.627: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.628: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.628: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.628: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.628: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.628: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.628: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.628: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.628: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.628: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.628: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.628: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.628: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.628: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.628: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.629: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.629: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.629: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.629: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.629: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.629: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.629: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.629: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.629: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.629: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.629: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.629: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.629: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.629: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.629: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.629: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.630: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.630: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.630: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.630: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.630: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.630: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.630: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.630: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.630: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.630: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.631: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.631: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.631: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.631: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.631: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.631: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.631: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.631: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.631: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.631: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.631: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.631: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.631: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.631: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.632: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.632: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.632: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.632: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.632: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.632: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.632: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.632: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.632: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.632: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.633: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.633: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.633: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.633: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.633: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.633: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.633: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.633: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.633: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.633: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.633: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.633: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.633: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.633: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.634: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.634: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.634: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.634: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.634: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.634: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.634: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.634: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.634: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.634: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.635: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.635: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.635: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.635: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.635: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.635: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.635: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.635: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.635: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.635: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.635: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.635: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.635: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.635: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.635: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.636: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.636: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.636: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.636: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.636: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.636: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.636: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.636: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.636: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.636: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.636: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.636: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.636: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.636: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.636: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.637: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.637: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.637: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.637: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.637: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.637: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.637: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.637: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.637: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.637: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.638: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.638: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.638: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.638: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.638: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.638: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.638: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.638: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.638: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.638: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.638: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.638: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.638: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.638: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.639: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.639: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.639: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.639: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.639: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.639: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.639: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.639: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.639: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.639: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.640: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.640: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.640: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.640: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.640: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.640: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.640: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.640: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.640: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.640: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.640: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.640: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.640: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.640: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.641: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.641: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.641: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.641: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.641: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.641: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.641: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.641: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.641: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.641: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.642: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.642: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.642: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.642: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.642: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.642: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.642: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.642: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.642: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.642: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.642: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.642: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.642: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.642: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.643: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.643: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.643: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.643: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.643: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.643: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.643: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.643: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.643: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.643: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.644: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.644: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.644: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.644: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.644: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.644: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.644: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.644: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.644: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.644: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.644: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.644: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.644: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.644: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.645: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.645: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.645: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.645: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.645: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.645: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.645: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.645: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.645: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.645: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.646: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.646: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.646: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.646: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.646: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.646: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.646: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.646: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.646: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.646: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.646: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.646: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.646: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.646: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.647: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.647: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.647: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.647: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.647: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.647: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.647: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.647: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.647: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.647: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.648: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.648: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.648: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.648: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.648: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.648: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.648: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.648: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.648: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.648: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.648: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.648: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.648: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.648: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.649: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.649: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.649: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.649: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.649: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.649: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.649: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.649: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.649: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.649: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.650: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.650: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.650: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.650: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.650: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.650: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.650: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.650: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.650: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.650: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.650: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.650: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.650: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.650: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.651: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.651: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.651: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.651: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.651: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.651: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.651: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.651: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.651: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.651: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.652: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.652: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.652: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.652: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.652: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.652: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.652: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.652: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.652: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.652: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.652: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.652: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.652: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.652: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.653: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.653: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.653: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.653: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.653: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.653: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.653: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.653: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.653: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.653: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.654: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.654: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.654: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.654: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.654: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.654: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.654: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.654: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.654: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.654: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.654: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.654: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.654: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.654: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.655: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.655: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.655: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.655: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.655: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.655: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.655: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.655: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.655: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.655: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.656: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.656: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.656: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.656: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.656: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.656: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.656: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.656: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.656: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.656: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.656: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.656: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.656: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.656: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.657: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.657: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.657: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.657: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.657: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.657: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.657: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.657: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.657: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.657: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.658: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.658: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.658: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.658: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.658: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.658: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.658: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.658: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.659: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.659: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.659: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.659: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.659: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.659: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.659: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.659: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.659: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.659: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.659: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.659: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.659: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.659: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.660: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.660: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.660: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.660: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.660: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.660: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.660: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.660: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.660: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.660: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.661: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.661: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.661: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.661: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.661: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.661: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.661: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.661: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.661: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.661: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.661: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.661: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.661: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.661: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.662: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.662: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.662: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.662: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.662: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.662: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.662: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.662: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.663: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.663: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.663: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.663: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.663: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.663: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.663: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.663: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.663: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.663: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.664: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.664: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.664: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.664: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.664: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.664: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.664: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.664: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.664: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.664: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.664: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.664: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.664: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.664: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.665: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.665: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.665: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.665: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.665: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.665: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.665: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.665: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.665: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.665: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.666: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.666: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.666: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.666: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.666: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.666: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.666: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.666: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.666: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.666: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.666: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.666: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.666: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.666: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.667: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.667: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.667: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.667: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.667: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.667: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.667: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.667: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.667: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.667: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.668: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.668: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.668: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.668: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.668: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.668: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.668: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.668: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.668: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.668: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.668: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.668: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.668: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.668: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.669: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.669: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.669: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.669: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.669: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.669: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.669: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.669: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.669: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.669: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.670: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.670: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.670: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.670: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.670: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.670: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.670: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.670: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.671: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.671: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.671: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.671: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.671: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.671: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.671: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.671: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.671: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.671: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.671: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.671: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.671: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.671: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.672: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.672: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.672: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.672: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.672: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.672: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.672: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.672: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.672: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.672: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.673: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.673: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.673: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.673: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.673: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.673: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.673: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.673: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.673: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.673: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.673: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.673: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.673: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.673: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.674: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.674: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.674: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.674: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.674: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.674: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.674: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.674: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.674: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.674: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.675: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.675: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.675: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.675: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.675: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.675: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.675: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.675: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.675: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.675: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.675: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.675: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.675: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.675: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.676: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.676: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.676: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.676: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.676: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.676: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.676: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.676: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.676: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.676: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.677: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.677: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.677: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.677: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.677: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.677: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.677: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.677: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.677: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.677: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.677: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.677: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.677: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.677: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.678: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.678: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.678: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.678: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.678: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.678: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.678: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.678: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.678: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.678: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.679: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.679: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.679: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.679: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.679: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.679: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.679: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.679: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.680: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.680: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.680: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.680: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.680: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.680: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.680: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.680: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.680: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.680: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.680: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.680: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.680: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.680: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.681: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.681: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.681: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.681: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.681: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.681: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.681: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.681: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.681: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.681: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.682: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.682: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.682: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.682: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.682: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.682: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.682: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.682: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.682: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.682: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.682: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.682: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.682: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.682: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.683: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.683: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.683: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.683: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.683: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.683: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.683: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.683: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.683: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.683: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.684: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.684: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.684: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.684: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.684: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.684: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.684: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.684: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.684: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.684: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.684: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.684: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.684: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.684: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.685: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.685: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.685: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.685: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.685: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.685: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.685: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.685: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.685: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.685: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.686: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.686: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.686: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.686: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.686: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.686: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.686: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.686: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.686: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.686: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.686: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.686: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.686: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.686: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.687: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.687: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.687: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.687: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.687: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.687: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.687: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.687: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.687: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.687: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.688: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.688: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.688: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.688: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.688: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.688: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.688: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.688: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.688: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.688: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.688: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.688: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.688: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.688: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.689: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.689: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.689: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.689: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.689: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.689: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.689: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.689: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.689: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.689: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.690: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.690: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.690: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.690: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.690: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.690: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.690: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.690: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.690: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.690: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.690: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.690: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.690: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.691: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.691: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.691: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.691: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.691: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.691: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.691: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.691: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.691: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.692: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.692: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.692: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.692: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.692: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.692: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.692: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.692: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.692: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.692: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.693: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.693: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.693: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.693: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.693: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.693: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.693: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.693: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.693: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.693: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.693: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.693: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.693: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.693: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.693: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.694: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.694: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.694: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.694: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.694: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.694: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.694: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.694: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.694: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.694: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.694: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.694: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.694: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.694: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.694: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.695: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.695: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.695: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.695: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.695: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.695: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.695: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.695: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.696: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.696: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.696: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.696: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.696: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.696: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.696: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.696: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.696: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.696: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.697: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.697: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.697: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.697: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.697: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.697: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.697: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.697: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.697: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.697: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.697: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.697: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.697: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.697: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.698: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.698: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.698: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.698: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.698: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.698: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.698: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.698: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.698: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.698: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.699: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.699: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.699: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.699: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.699: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.699: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.699: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.699: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.699: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.699: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.699: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.699: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.699: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.699: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.699: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.699: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.700: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.700: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.700: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.700: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.700: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.700: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.700: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.700: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.701: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.701: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.701: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.701: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.701: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.701: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.701: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.701: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.701: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.701: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.701: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.701: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.701: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.701: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.702: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.702: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.702: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.702: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.702: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.702: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.702: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.702: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.702: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.702: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.703: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.703: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.703: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.703: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.703: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.703: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.703: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.703: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.703: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.703: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.703: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.703: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.703: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.703: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.704: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.704: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.704: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.704: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.704: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.704: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.704: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.704: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.704: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.704: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.705: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.705: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.705: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.705: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.705: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.705: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.705: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.705: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.705: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.705: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.705: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.705: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.705: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.705: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.706: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.706: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.706: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.706: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.706: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.706: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.706: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.706: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.706: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.706: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.707: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.707: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.707: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.707: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.707: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.707: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.707: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.707: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.707: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.707: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.707: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.707: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.707: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.707: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.708: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.708: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.708: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.708: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.708: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.708: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.708: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.708: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.708: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.708: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.709: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.709: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.709: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.709: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.709: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.709: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.709: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.709: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.709: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.709: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.709: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.709: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.709: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.709: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.710: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.710: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.710: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.710: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.710: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.710: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.710: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.710: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.710: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.710: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.711: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.711: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.711: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.711: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.711: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.711: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.711: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.711: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.712: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.712: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.712: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.712: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.712: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.712: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.712: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.712: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.712: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.712: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.712: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.712: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.712: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.712: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.713: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.713: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.713: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.713: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.713: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.713: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.713: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.713: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.713: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.713: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.714: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.714: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.714: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.714: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.714: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.714: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.714: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.714: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.714: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.714: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.714: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.714: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.714: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.714: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.715: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.715: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.715: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.715: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.715: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.715: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.715: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.715: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.715: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.715: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.716: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.716: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.716: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.716: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.716: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.716: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.716: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.716: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.717: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.717: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.717: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.717: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.717: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.717: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.717: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.717: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.717: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.717: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.717: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.717: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.717: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.717: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.717: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.717: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.718: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.718: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.718: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.718: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.718: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.718: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.718: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.718: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.718: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.718: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.718: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.718: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.718: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.718: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.719: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.719: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.719: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.719: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.719: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.719: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.719: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.719: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.719: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.719: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.720: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.720: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.720: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.720: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.720: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.720: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.720: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.720: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.720: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.720: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.720: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.720: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.720: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.720: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.721: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.721: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.721: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.721: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.721: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.721: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.721: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.721: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.721: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.721: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.722: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.722: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.722: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.722: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.722: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.722: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.722: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.722: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.722: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.723: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.723: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.723: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.723: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.723: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.723: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.723: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.723: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.723: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.723: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.723: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.723: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.723: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.723: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.723: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.724: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.724: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.724: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.724: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.724: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.724: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.724: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.724: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.724: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.724: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.724: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.724: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.724: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.724: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.725: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.725: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.725: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.725: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.725: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.725: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.725: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.725: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.725: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.725: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.726: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.726: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.726: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.726: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.726: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.726: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.726: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.726: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.726: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.726: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.726: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.726: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.726: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.726: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.727: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.727: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.727: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.727: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.727: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.727: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.727: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.727: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.727: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.727: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.728: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.728: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.728: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.728: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.728: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.728: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.728: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.728: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.728: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.728: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.728: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.728: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.728: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.728: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.729: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.729: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.729: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.729: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.729: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.729: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.729: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.729: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.729: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.729: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.730: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.730: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.730: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.730: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.730: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.730: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.730: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.730: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.730: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.730: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.730: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.730: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.730: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.730: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.731: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.731: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.731: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.731: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.731: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.731: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.731: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.731: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.731: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.731: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.732: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.732: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.732: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.732: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.732: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.732: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.732: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.732: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.732: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.732: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.732: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.732: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.732: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.732: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.733: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.733: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.733: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.733: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.733: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.733: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.733: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.733: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.733: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.733: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.734: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.734: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.734: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.734: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.734: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.734: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.734: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.734: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.734: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.734: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.734: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.734: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.734: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.735: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.735: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.735: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.735: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.735: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.735: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.736: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.736: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.736: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.736: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.736: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.736: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.736: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.737: [vfs7552] CAPTURE_NUM_STATES entering state 4
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.737: Cleaning image
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.737: variance_after = 20
172s 
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.737: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.737: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.737: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.737: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.737: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.737: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.737: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.738: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.738: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.738: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.738: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.738: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.738: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.738: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.738: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.738: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.738: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.738: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.738: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.739: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.739: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.739: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.739: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.739: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.739: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.739: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.739: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.739: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.739: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.740: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.740: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.740: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.740: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.740: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.740: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.740: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.740: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.740: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.740: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.740: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.740: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.740: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.740: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.741: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.741: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.741: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.741: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.741: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.741: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.741: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.741: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.741: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.741: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.742: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.742: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.742: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.742: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.742: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.742: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.742: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.742: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.742: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.742: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.742: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.742: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.742: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.742: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.742: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.743: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.743: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.743: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.743: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.743: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.743: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.743: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.743: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.743: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.744: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.744: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.744: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.744: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.744: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.744: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.744: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.744: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.744: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.744: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.744: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.744: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.744: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.744: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.745: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.745: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.745: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.745: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.745: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.745: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.745: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.745: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.745: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.745: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.745: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.745: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.746: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.746: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.746: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.746: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.746: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.746: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.746: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.746: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.746: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.746: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.746: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.746: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.746: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.746: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.747: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.747: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.747: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.747: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.747: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.747: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.747: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.747: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.747: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.747: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.747: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.747: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.747: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.747: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.748: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.748: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.748: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.748: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.748: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.748: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.748: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.748: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.748: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.748: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.749: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.749: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.749: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.749: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.749: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.749: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.749: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.749: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.749: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.749: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.749: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.749: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.749: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.749: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.750: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.750: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.750: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.750: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.750: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.750: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.750: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.750: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.750: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.750: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.751: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.751: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.751: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.751: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.751: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.751: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.751: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.751: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.751: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.751: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.751: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.751: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.751: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.751: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.752: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.752: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.752: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.752: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.752: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.752: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.752: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.752: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.752: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.752: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.752: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.752: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.752: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.752: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.752: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.752: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.752: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.752: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.753: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.753: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.753: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.753: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.753: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.753: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.753: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.753: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.753: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.753: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.753: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.753: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.753: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.753: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.753: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.753: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.754: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.754: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.754: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.754: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.754: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.754: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.754: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.754: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.754: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.754: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.754: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.754: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.754: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.754: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.755: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.755: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.755: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.755: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.755: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.755: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.755: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.755: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.755: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.755: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.756: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.756: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.756: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.756: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.756: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.756: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.756: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.756: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.756: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.756: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.756: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.756: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.756: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.756: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.757: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.757: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.757: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.757: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.757: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.757: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.757: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.757: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.757: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.757: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.758: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.758: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.758: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.758: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.758: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.758: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.758: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.758: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.758: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.758: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.758: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.758: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.758: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.758: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.759: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.759: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.759: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.759: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.759: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.759: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.759: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.759: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.759: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.759: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.760: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.760: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.760: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.760: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.760: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.760: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.760: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.760: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.760: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.760: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.760: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.760: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.760: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.760: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.761: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.761: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.761: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.761: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.761: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.761: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.761: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.761: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.762: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.762: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.762: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.762: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.762: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.762: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.762: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.762: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.762: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.762: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.763: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.763: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.763: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.763: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.763: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.763: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.763: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.763: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.763: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.763: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.763: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.763: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.763: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.763: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.764: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.764: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.764: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.764: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.764: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.764: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.764: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.764: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.764: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.764: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.765: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.765: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.765: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.765: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.765: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.765: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.765: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.765: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.766: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.766: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.766: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.766: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.766: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.766: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.766: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.766: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.766: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.766: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.766: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.766: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.766: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.766: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.767: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.767: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.767: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.767: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.767: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.767: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.767: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.767: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.767: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.767: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.768: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.768: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.768: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.768: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.768: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.768: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.768: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.768: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.768: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.768: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.768: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.768: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.768: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.768: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.768: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.769: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.769: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.769: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.769: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.769: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.769: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.769: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.769: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.769: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.769: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.769: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.769: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.769: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.769: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.769: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.770: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.770: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.770: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.770: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.770: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.770: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.770: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.770: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.770: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.770: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.771: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.771: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.771: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.771: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.771: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.771: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.771: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.771: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.771: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.771: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.771: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.771: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.771: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.771: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.772: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.772: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.772: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.772: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.772: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.772: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.772: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.772: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.772: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.772: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.773: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.773: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.773: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.773: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.773: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.773: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.773: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.773: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.774: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.774: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.774: [vfs7552] CAPTURE_NUM_STATES entering state 4
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.774: Cleaning image
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.774: variance_after = 18
172s 
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.774: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.774: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.774: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.775: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.775: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.775: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.775: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.775: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.775: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.775: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.775: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.775: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.775: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.776: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.776: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.776: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.776: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.776: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.776: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.776: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.776: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.776: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.776: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.776: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.776: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.776: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.776: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.777: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.777: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.777: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.777: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.777: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.777: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.777: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.777: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.777: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.777: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.778: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.778: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.778: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.778: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.778: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.778: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.778: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.778: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.778: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.778: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.778: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.778: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.778: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.778: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.779: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.779: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.779: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.779: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.779: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.779: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.779: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.779: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.779: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.779: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.780: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.780: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.780: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.780: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.780: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.780: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.780: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.780: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.780: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.780: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.780: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.780: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.780: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.780: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.781: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.781: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.781: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.781: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.781: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.781: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.781: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.781: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.781: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.781: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.782: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.782: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.782: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.782: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.782: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.782: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.782: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.782: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.782: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.782: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.782: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.782: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.782: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.782: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.783: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.783: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.783: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.783: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.783: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.783: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.783: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.783: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.783: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.783: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.784: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.784: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.784: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.784: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.784: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.784: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.784: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.784: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.785: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.785: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.785: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.785: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.785: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.785: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.785: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.785: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.785: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.785: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.785: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.785: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.785: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.785: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.786: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.786: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.786: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.786: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.786: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.786: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.786: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.786: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.786: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.786: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.787: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.787: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.787: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.787: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.787: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.787: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.787: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.787: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.787: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.787: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.787: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.787: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.787: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.787: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.788: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.788: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.788: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.788: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.788: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.788: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.788: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.788: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.788: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.788: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.789: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.789: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.789: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.789: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.789: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.789: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.789: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.789: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.789: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.790: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.790: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.790: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.790: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.790: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.790: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.790: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.790: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.790: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.790: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.790: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.790: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.790: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.791: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.791: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.791: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.791: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.791: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.791: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.791: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.791: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.791: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.791: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.792: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.792: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.792: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.792: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.792: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.792: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.792: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.792: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.792: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.792: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.792: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.792: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.792: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.792: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.793: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.793: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.793: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.793: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.793: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.793: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.793: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.793: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.793: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.793: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.794: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.794: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.794: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.794: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.794: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.794: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.794: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.794: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.794: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.794: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.794: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.794: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.794: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.794: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.795: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.795: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.795: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.795: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.795: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.795: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.795: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.795: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.795: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.795: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.796: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.796: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.796: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.796: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.796: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.796: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.796: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.796: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.796: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.796: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.796: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.796: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.796: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.796: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.797: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.797: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.797: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.797: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.797: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.797: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.797: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.797: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.797: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.797: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.798: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.798: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.798: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.798: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.798: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.798: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.798: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.798: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.798: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.798: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.798: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.798: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.798: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.798: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.799: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.799: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.799: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.799: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.799: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.799: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.799: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.799: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.799: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.799: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.800: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.800: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.800: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.800: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.800: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.800: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.800: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.800: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.800: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.800: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.800: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.800: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.800: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.800: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.801: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.801: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.801: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.801: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.801: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.801: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.801: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.801: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.801: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.801: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.802: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.802: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.802: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.802: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.802: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.802: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.802: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.802: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.802: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.802: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.802: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.802: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.802: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.802: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.803: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.803: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.803: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.803: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.803: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.803: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.803: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.803: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.803: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.803: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.804: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.804: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.804: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.804: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.804: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.804: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.804: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.804: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.804: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.804: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.804: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.804: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.804: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.804: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.805: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.805: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.805: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.805: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.805: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.805: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.805: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.805: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.805: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.806: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.806: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.806: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.806: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.806: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.806: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.806: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.806: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.806: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.806: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.806: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.806: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.806: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.806: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.806: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.807: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.807: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.807: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.807: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.807: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.807: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.807: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.807: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.807: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.807: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.808: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.808: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.808: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.808: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.808: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.808: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.808: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.808: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.808: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.808: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.808: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.808: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.808: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.808: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.809: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.809: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.809: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.809: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.809: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.809: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.809: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.809: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.809: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.809: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.810: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.810: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.810: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.810: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.810: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.810: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.810: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.810: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.810: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.810: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.810: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.810: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.810: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.810: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.811: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.811: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.811: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.811: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.811: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.811: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.811: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.811: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.811: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.811: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.812: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.812: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.812: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.812: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.812: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.812: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.812: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.812: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.812: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.812: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.812: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.813: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.813: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.813: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.813: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.813: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.813: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.813: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.814: [vfs7552] CAPTURE_NUM_STATES entering state 4
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.814: Cleaning image
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.814: variance_after = 18
172s 
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.814: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.814: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.814: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.814: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.814: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.814: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.814: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.814: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.814: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.814: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.815: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.815: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.815: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.815: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.815: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.815: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.815: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.815: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.815: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.815: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.815: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.816: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.816: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.816: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.816: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.816: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.816: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.816: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.816: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.816: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.816: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.816: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.816: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.816: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.816: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.817: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.817: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.817: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.817: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.817: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.817: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.817: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.817: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.817: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.817: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.818: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.818: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.818: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.818: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.818: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.818: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.818: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.818: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.818: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.818: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.818: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.818: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.818: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.818: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.818: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.819: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.819: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.819: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.819: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.819: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.819: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.819: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.819: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.819: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.819: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.819: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.819: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.819: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.819: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.819: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.820: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.820: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.820: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.820: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.820: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.820: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.820: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.820: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.821: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.821: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.821: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.821: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.821: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.821: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.821: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.821: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.821: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.821: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.821: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.821: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.821: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.821: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.821: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.821: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.822: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.822: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.822: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.822: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.822: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.822: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.822: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.822: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.822: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.822: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.822: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.822: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.822: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.822: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.822: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.822: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.823: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.823: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.823: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.823: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.823: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.823: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.823: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.823: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.823: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.823: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.824: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.824: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.824: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.824: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.824: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.824: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.824: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.824: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.824: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.824: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.824: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.824: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.824: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.824: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.825: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.825: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.825: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.825: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.825: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.825: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.825: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.825: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.825: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.825: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.826: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.826: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.826: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.826: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.826: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.826: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.826: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.826: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.826: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.826: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.826: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.826: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.826: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.826: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.826: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.826: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.827: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.827: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.827: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.827: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.827: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.827: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.827: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.827: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.827: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.827: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.827: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.827: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.827: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.827: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.828: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.828: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.828: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.828: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.828: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.828: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.828: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.828: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.828: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.828: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.829: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.829: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.829: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.829: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.829: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.829: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.829: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.829: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.829: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.829: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.829: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.829: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.829: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.829: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.829: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.829: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.830: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.830: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.830: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.830: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.830: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.830: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.830: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.830: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.830: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.830: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.830: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.830: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.830: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.830: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.831: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.831: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.831: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.831: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.831: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.831: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.831: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.831: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.832: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.832: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.832: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.832: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.832: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.832: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.832: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.832: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.832: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.832: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.833: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.833: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.833: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.833: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.833: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.833: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.833: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.833: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.833: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.833: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.833: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.833: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.833: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.833: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.833: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.833: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.834: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.834: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.834: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.834: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.834: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.834: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.834: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.834: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.834: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.834: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.834: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.834: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.834: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.834: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.835: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.835: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.835: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.835: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.835: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.835: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.835: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.835: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.835: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.835: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.836: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.836: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.836: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.836: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.836: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.836: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.836: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.836: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.836: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.836: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.836: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.836: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.836: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.836: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.837: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.837: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.837: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.837: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.837: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.837: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.837: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.837: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.837: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.838: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.838: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.838: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.838: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.838: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.838: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.838: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.838: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.838: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.839: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.839: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.839: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.839: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.839: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.839: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.839: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.839: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.839: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.839: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.839: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.839: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.839: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.839: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.839: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.839: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.840: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.840: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.840: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.840: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.840: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.840: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.840: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.840: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.840: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.840: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.840: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.840: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.840: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.840: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.841: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.841: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.841: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.841: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.841: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.841: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.841: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.841: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.841: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.841: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.842: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.842: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.842: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.842: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.842: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.842: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.842: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.842: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.842: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.842: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.843: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.843: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.843: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.843: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.843: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.843: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.843: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.843: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.843: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.843: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.843: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.843: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.843: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.843: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.844: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.844: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.844: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.844: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.844: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.844: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.844: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.844: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.844: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.845: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.845: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.845: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.845: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.845: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.845: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.845: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.845: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.845: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.845: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.845: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.845: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.845: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.845: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.846: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.846: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.846: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.846: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.846: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.846: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.846: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.846: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.846: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.846: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.846: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.846: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.846: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.846: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.846: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.847: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.847: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.847: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.847: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.847: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.847: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.847: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.847: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.847: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.847: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.848: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.848: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.848: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.848: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.848: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.848: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.848: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.848: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.848: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.848: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.848: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.848: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.848: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.848: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.848: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.848: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.849: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.849: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.849: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.849: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.849: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.849: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.849: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.849: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.849: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.849: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.849: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.849: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.849: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.849: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.850: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.850: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.850: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.850: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.850: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.850: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.850: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.850: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.850: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.850: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.851: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.851: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.851: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.851: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.851: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.851: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.851: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.851: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.851: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.851: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.851: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.851: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.851: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.851: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.852: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.852: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.852: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.852: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.852: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.852: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.852: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.852: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.852: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.852: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.853: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.853: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.853: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.853: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.853: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.853: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.853: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.853: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.853: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.853: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.853: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.853: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.853: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.853: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.854: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.854: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.854: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.854: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.854: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.854: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.854: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.854: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.854: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.855: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.855: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.855: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.855: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.855: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.855: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.855: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.855: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.855: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.855: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.855: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.855: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.855: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.855: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.855: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.856: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.856: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.856: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.856: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.856: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.856: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.856: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.856: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.856: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.856: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.857: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.857: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.857: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.857: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.857: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.857: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.857: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.857: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.857: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.857: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.857: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.857: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.857: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.858: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.858: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.858: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.858: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.858: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.858: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.858: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.858: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.858: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.858: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.858: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.859: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.859: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.859: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.859: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.859: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.859: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.859: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.859: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.859: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.859: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.859: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.859: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.859: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.859: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.860: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.860: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.860: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.860: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.860: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.860: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.860: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.860: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.860: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.860: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.861: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.861: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.861: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.861: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.861: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.861: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.861: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.861: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.861: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.861: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.861: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.861: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.861: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.861: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.862: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.862: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.862: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.862: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.862: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.862: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.862: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.862: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.862: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.862: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.863: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.863: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.863: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.863: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.863: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.863: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.863: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.863: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.863: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.863: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.863: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.863: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.863: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.863: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.863: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.863: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.864: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.864: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.864: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.864: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.864: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.864: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.864: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.864: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.864: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.864: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.864: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.864: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.864: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.864: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.865: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.865: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.865: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.865: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.865: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.865: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.865: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.865: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.865: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.866: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.866: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.866: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.866: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.866: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.866: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.866: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.866: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.866: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.867: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.867: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.867: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.867: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.867: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.867: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.867: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.867: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.867: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.867: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.867: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.867: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.867: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.867: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.867: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.868: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.868: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.868: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.868: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.868: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.868: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.868: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.868: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.868: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.868: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.868: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.868: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.868: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.868: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.868: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.869: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.869: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.869: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.869: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.869: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.869: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.869: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.869: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.869: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.869: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.870: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.870: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.870: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.870: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.870: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.870: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.870: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.870: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.870: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.870: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.870: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.870: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.870: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.870: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.871: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.871: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.871: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.871: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.871: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.871: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.871: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.871: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.871: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.871: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.872: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.872: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.872: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.872: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.872: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.872: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.872: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.872: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.873: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.873: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.873: [vfs7552] CAPTURE_NUM_STATES entering state 4
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.873: Cleaning image
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.873: variance_after = 18
172s 
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.873: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.873: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.873: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.873: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.873: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.874: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.874: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.874: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.874: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.874: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.874: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.874: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.874: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.875: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.875: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.875: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.875: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.875: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.875: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.875: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.875: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.875: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.875: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.875: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.875: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.875: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.875: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.876: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.876: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.876: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.876: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.876: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.876: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.876: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.876: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.876: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.876: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.877: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.877: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.877: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.877: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.877: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.877: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.877: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.877: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.877: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.877: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.877: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.877: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.877: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.877: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.877: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.878: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.878: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.878: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.878: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.878: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.878: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.878: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.878: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.878: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.879: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.879: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.879: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.879: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.879: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.879: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.879: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.879: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.879: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.879: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.879: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.879: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.879: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.879: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.879: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.880: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.880: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.880: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.880: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.880: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.880: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.880: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.880: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.880: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.881: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.881: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.881: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.881: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.881: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.881: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.881: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.881: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.881: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.881: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.881: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.881: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.881: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.881: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.882: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.882: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.882: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.882: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.882: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.882: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.882: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.882: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.882: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.882: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.883: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.883: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.883: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.883: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.883: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.883: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.883: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.883: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.883: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.883: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.883: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.883: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.883: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.883: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.884: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.884: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.884: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.884: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.884: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.884: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.884: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.884: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.884: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.884: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.885: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.885: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.885: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.885: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.885: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.885: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.885: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.885: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.885: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.885: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.885: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.885: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.885: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.885: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.886: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.886: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.886: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.886: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.886: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.886: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.886: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.886: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.886: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.886: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.887: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.887: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.887: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.887: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.887: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.887: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.887: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.887: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.887: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.887: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.887: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.887: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.887: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.887: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.888: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.888: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.888: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.888: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.888: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.888: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.888: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.888: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.888: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.888: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.889: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.889: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.889: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.889: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.889: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.889: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.889: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.889: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.889: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.889: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.889: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.889: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.889: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.889: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.890: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.890: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.890: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.890: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.890: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.890: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.890: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.890: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.890: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.890: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.891: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.891: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.891: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.891: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.891: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.891: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.891: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.891: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.891: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.892: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.892: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.892: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.892: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.892: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.892: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.892: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.892: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.892: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.892: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.892: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.892: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.892: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.893: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.893: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.893: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.893: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.893: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.893: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.893: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.893: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.893: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.893: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.894: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.894: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.894: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.894: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.894: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.894: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.894: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.894: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.894: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.894: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.894: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.894: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.894: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.894: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.895: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.895: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.895: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.895: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.895: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.895: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.895: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.895: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.895: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.895: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.896: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.896: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.896: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.896: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.896: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.896: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.896: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.896: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.896: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.896: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.896: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.896: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.896: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.896: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.897: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.897: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.897: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.897: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.897: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.897: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.897: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.897: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.897: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.897: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.897: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.897: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.897: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.897: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.897: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.897: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.898: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.898: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.898: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.898: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.898: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.898: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.898: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.898: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.898: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.898: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.899: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.899: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.899: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.899: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.899: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.899: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.899: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.899: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.899: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.899: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.899: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.899: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.899: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.899: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.899: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.899: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.900: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.900: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.900: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.900: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.900: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.900: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.900: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.900: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.900: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.900: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.900: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.900: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.900: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.900: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.901: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.901: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.901: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.901: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.901: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.901: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.901: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.901: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.901: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.901: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.902: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.902: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.902: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.902: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.902: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.902: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.902: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.902: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.902: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.902: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.902: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.902: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.902: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.902: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.903: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.903: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.903: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.903: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.903: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.903: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.903: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.903: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.903: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.903: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.903: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.903: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.903: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.903: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.903: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.903: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.904: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.904: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.904: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.904: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.904: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.904: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.904: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.904: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.904: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.904: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.905: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.905: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.905: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.905: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.905: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.905: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.905: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.905: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.905: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.905: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.905: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.905: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.905: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.905: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.905: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.906: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.906: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.906: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.906: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.906: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.906: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.906: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.906: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.906: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.906: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.906: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.906: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.906: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.906: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.906: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.907: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.907: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.907: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.907: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.907: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.907: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.907: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.907: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.907: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.907: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.907: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.907: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.907: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.907: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.907: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.907: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.908: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.908: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.908: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.908: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.908: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.908: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.908: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.908: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.908: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.908: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.909: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.909: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.909: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.909: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.909: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.909: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.909: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.909: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.909: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.909: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.909: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.909: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.909: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.909: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.910: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.910: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.910: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.910: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.910: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.910: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.910: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.910: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.910: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.910: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.911: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.911: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.911: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.911: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.911: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.911: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.911: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.911: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.911: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.912: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.912: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.912: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.912: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.912: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.912: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.912: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.912: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.912: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.912: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.912: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.912: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.912: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.912: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.913: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.913: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.913: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.913: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.913: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.913: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.913: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.913: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.913: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.914: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.914: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.914: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.914: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.914: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.914: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.914: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.914: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.914: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.914: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.914: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.914: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.914: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.914: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.915: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.915: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.915: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.915: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.915: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.915: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.915: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.915: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.915: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.915: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.916: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.916: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.916: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.916: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.916: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.916: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.916: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.916: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.916: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.916: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.916: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.916: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.916: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.916: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.916: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.916: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.917: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.917: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.917: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.917: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.917: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.917: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.917: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.917: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.917: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.917: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.917: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.917: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.917: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.917: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.918: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.918: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.918: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.918: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.918: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.918: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.918: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.918: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.918: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.918: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.919: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.919: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.919: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.919: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.919: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.919: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.919: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.919: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.919: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.919: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.919: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.919: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.919: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.919: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.920: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.920: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.920: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.920: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.920: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.920: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.920: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.920: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.920: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.920: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.920: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.921: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.921: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.921: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.921: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.921: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.921: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.921: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.921: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.921: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.921: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.921: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.921: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.921: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.921: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.921: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.922: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.922: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.922: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.922: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.922: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.922: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.922: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.922: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.922: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.922: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.922: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.922: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.922: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.922: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.923: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.923: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.923: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.923: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.923: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.923: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.923: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.923: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.923: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.923: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.924: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.924: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.924: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.924: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.924: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.924: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.924: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.924: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.924: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.924: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.924: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.924: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.924: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.924: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.925: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.925: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.925: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.925: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.925: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.925: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.925: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.925: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.925: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.925: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.926: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.926: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.926: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.926: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.926: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.926: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.926: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.926: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.926: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.926: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.926: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.926: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.926: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.926: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.927: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.927: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.927: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.927: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.927: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.927: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.927: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.927: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.927: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.927: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.927: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.927: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.927: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.927: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.927: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.927: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.928: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.928: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.928: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.928: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.928: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.928: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.928: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.928: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.928: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.928: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.929: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.929: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.929: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.929: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.929: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.929: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.929: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.929: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.929: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.929: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.929: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.929: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.929: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.929: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.929: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.929: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.930: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.930: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.930: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.930: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.930: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.930: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.930: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.930: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.930: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.930: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.930: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.930: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.930: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.930: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.931: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.931: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.931: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.931: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.931: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.931: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.931: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.931: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.931: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.931: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.932: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.932: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.932: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.932: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.932: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.932: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.932: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.932: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.932: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.932: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.932: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.932: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.932: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.932: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.933: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.933: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.933: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.933: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.933: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.933: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.933: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.933: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.933: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.933: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.933: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.933: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.933: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.933: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.933: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.933: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.934: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.934: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.934: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.934: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.934: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.934: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.934: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.934: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.934: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.934: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.935: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.935: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.935: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.935: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.935: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.935: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.935: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.935: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.935: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.935: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.935: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.935: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.935: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.935: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.936: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.936: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.936: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.936: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.936: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.936: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.936: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.936: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.936: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.936: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.936: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.936: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.936: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.936: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.936: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.936: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.937: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.937: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.937: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.937: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.937: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.937: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.937: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.937: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.937: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.937: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.938: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.938: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.938: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.938: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.938: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.938: [vfs7552] CAPTURE_NUM_STATES entering state 2
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.938: [vfs7552] REQUEST CHUNK entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.938: Sending vfs7552_read_image_chunk
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.939: [vfs7552] REQUEST CHUNK completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.939: [vfs7552] CAPTURE_NUM_STATES entering state 3
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.939: [vfs7552] CAPTURE_NUM_STATES entering state 4
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.939: Cleaning image
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.939: variance_after = 18
172s 
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.939: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.939: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.939: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.939: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.939: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.940: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.940: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.940: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.940: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.940: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.940: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.940: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.940: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.940: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.940: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.940: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.940: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.940: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.940: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.941: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.941: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.941: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.941: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.941: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.941: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.941: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.941: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.941: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.941: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.942: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.942: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.942: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.942: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.942: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.942: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.942: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.942: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.942: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.942: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.942: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.942: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.942: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.942: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.942: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.942: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.943: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.943: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.943: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.943: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.943: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.943: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.943: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.943: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.943: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.943: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.943: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.943: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.943: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.943: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.944: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.944: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.944: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.944: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.944: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.944: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.944: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.944: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.944: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.944: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.944: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.944: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.944: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.944: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.944: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.944: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.945: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.945: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.945: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.945: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.945: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.945: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.945: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.945: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.945: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.945: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.946: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.946: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.946: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.946: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.946: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.946: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.946: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.946: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.946: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.946: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.946: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.946: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.946: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.946: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.947: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.947: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.947: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.947: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.947: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.947: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.947: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.947: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.947: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.947: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.947: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.948: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.948: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.948: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.948: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.948: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.948: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.948: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.948: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.948: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.948: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.948: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.948: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.948: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.948: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.948: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.949: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.949: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.949: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.949: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.949: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.949: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.949: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.949: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.949: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.949: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.949: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.949: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.949: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.949: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.950: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.950: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.950: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.950: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.950: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.950: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.950: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.950: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.950: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.950: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.951: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.951: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.951: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.951: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.951: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.951: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.951: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.951: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.951: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.951: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.951: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.951: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.951: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.951: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.951: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.951: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.952: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.952: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.952: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.952: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.952: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.952: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.952: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.952: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.952: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.952: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.952: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.952: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.952: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.952: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.953: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.953: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.953: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.953: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.953: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.953: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.953: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.953: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.953: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.953: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.954: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.954: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.954: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.954: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.954: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.954: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.954: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.954: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.954: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.954: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.954: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.954: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.954: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.954: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.955: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.955: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.955: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.955: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.955: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.955: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.955: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.955: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.955: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.955: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.955: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.955: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.955: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.955: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.955: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.955: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.956: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.956: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.956: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.956: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.956: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.956: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.956: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.956: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.956: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.956: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.957: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.957: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.957: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.957: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.957: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.957: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.957: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.957: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.957: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.957: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.957: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.957: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.957: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.957: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.958: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.958: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.958: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.958: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.958: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.958: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.958: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.958: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.958: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.958: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.958: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.958: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.958: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.958: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.958: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.958: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.959: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.959: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.959: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.959: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.959: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.959: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.959: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.959: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.959: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.959: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.959: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.959: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.959: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.959: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.959: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.959: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.960: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.960: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.960: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.960: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.960: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.960: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.960: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.960: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.960: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.961: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.961: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.961: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.961: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.961: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.961: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.961: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.961: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.961: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.962: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.962: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.962: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.962: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.962: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.962: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.962: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.962: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.962: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.962: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.962: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.962: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.962: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.962: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.962: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.962: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.963: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.963: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.963: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.963: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.963: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.963: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.963: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.963: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.963: Got 6 bytes out of 64
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.963: [vfs7552] QUERY DATA READY completed successfully
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.964: [vfs7552] CAPTURE_NUM_STATES entering state 1
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.964: [vfs7552] CAPTURE_NUM_STATES entering state 0
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.964: [vfs7552] QUERY DATA READY entering state 0
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.964: Sending vfs7552_is_image_ready
172s (process:2479): libfprint-SSM-DEBUG: 05:03:03.964: [vfs7552] QUERY DATA READY entering state 1
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.964: Receiving 64 bytes
172s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.964: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.964: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.964: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.964: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.964: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.964: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.964: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.964: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.965: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.965: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.965: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.965: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.965: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.965: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.965: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.965: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.965: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.965: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.965: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.965: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.965: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.965: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.966: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.966: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.966: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.966: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.966: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.966: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.966: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.967: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.967: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.967: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.967: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.967: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.968: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.968: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.968: variance_after = 17
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.968: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.968: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.968: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.968: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.968: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.968: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.968: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.968: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.968: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.968: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.968: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.969: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.969: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.969: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.969: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.969: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.969: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.969: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.969: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.969: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.969: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.970: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.970: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.970: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.970: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.970: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.970: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.970: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.970: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.970: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.970: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.970: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.970: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.970: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.970: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.971: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.971: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.971: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.971: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.971: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.971: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.971: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.971: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.971: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.971: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.971: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.971: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.971: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.971: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.971: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.971: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.972: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.972: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.972: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.972: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.972: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.972: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.972: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.972: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.972: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.972: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.973: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.973: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.973: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.973: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.973: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.973: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.973: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.973: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.973: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.973: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.973: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.973: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.973: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.973: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.974: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.974: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.974: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.974: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.974: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.974: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.974: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.974: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.974: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.974: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.975: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.975: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.975: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.975: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.975: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.975: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.975: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.975: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.975: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.975: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.975: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.975: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.975: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.975: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.976: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.976: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.976: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.976: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.976: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.976: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.976: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.976: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.976: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.976: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.977: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.977: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.977: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.977: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.977: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.977: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.977: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.977: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.977: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.977: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.977: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.977: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.977: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.977: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.977: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.978: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.978: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.978: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.978: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.978: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.978: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.978: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.978: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.978: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.979: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.979: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.979: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.979: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.979: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.979: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.979: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.979: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.979: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.979: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.979: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.979: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.979: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.979: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.980: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.980: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.980: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.980: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.980: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.980: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.980: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.980: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.980: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.980: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.981: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.981: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.981: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.981: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.981: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.981: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.981: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.981: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.981: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.981: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.981: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.981: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.981: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.981: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.982: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.982: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.982: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.982: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.982: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.982: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.982: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.982: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.982: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.982: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.983: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.983: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.983: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.983: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.983: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.983: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.983: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.983: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.983: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.983: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.983: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.983: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.983: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.983: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.984: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.984: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.984: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.984: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.984: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.984: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.984: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.984: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.984: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.984: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.984: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.984: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.984: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.984: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.984: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.984: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.985: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.985: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.985: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.985: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.985: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.985: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.985: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.985: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.985: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.985: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.986: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.986: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.986: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.986: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.986: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.986: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.986: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.986: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.986: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.986: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.986: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.986: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.986: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.986: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.987: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.987: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.987: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.987: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.987: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.987: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.987: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.987: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.987: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.987: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.987: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.988: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.988: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.988: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.988: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.988: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.988: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.988: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.988: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.988: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.988: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.988: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.988: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.988: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.989: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.989: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.989: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.989: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.989: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.989: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.989: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.989: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.989: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.989: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.990: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.990: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.990: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.990: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.990: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.990: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.990: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.990: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.990: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.990: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.990: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.990: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.990: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.990: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.990: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.990: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.991: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.991: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.991: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.991: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.991: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.991: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.991: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.991: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.991: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.991: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.991: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.991: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.991: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.991: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.992: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.992: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.992: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.992: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.992: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.992: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.992: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.992: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.992: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.992: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.993: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.993: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.993: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.993: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.993: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.993: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.993: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.993: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.993: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.993: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.993: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.993: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.993: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.993: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.994: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.994: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.994: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.994: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.994: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.994: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.994: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.994: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.994: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.994: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.995: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.995: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.995: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.995: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.995: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.995: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.995: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.995: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.995: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.995: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.995: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.995: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.995: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.995: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.995: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.995: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.996: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.996: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.996: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.996: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.996: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.996: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.996: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.996: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.997: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.997: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.997: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.997: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.997: variance_after = 16
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.997: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.997: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.997: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.997: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.998: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.998: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.998: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.998: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.998: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.998: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.998: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.998: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.998: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.999: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.999: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.999: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.999: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.999: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.999: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.999: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.999: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.999: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.999: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.999: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.999: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.999: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:03.999: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:03.999: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.000: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.000: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.000: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.000: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.000: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.000: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.000: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.000: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.000: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.000: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.000: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.000: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.000: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.000: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.000: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.001: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.001: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.001: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.001: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.001: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.001: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.001: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.001: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.001: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.001: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.001: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.001: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.001: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.001: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.001: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.001: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.002: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.002: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.002: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.002: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.002: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.002: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.002: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.002: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.002: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.002: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.002: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.002: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.002: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.002: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.002: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.002: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.003: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.003: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.003: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.003: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.003: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.003: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.003: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.003: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.003: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.003: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.004: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.004: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.004: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.004: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.004: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.004: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.004: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.004: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.004: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.004: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.004: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.004: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.004: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.004: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.005: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.005: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.005: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.005: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.005: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.005: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.005: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.005: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.005: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.005: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.005: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.005: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.005: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.005: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.006: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.006: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.006: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.006: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.006: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.006: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.006: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.006: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.006: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.006: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.006: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.006: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.007: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.007: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.007: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.007: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.007: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.007: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.007: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.007: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.007: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.007: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.007: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.007: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.007: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.007: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.008: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.008: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.008: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.008: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.008: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.008: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.008: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.008: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.008: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.008: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.009: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.009: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.009: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.009: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.009: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.009: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.009: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.009: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.009: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.009: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.009: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.009: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.009: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.009: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.009: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.010: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.010: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.010: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.010: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.010: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.010: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.010: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.010: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.010: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.010: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.010: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.010: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.010: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.010: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.010: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.011: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.011: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.011: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.011: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.011: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.011: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.011: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.011: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.011: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.011: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.012: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.012: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.012: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.012: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.012: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.012: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.012: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.012: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.012: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.012: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.012: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.012: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.012: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.012: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.012: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.012: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.013: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.013: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.013: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.013: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.013: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.013: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.013: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.013: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.013: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.013: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.013: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.013: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.013: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.013: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.013: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.013: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.014: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.014: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.014: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.014: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.014: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.014: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.014: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.014: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.014: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.014: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.014: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.014: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.014: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.014: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.015: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.015: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.015: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.015: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.015: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.015: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.015: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.015: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.015: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.015: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.015: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.015: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.015: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.015: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.015: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.015: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.016: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.016: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.016: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.016: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.016: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.016: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.016: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.016: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.016: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.016: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.017: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.017: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.017: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.017: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.017: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.017: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.017: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.017: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.017: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.017: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.017: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.017: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.017: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.017: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.018: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.018: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.018: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.018: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.018: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.018: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.018: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.018: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.019: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.019: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.019: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.019: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.019: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.019: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.019: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.019: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.019: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.019: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.019: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.019: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.019: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.019: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.019: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.019: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.020: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.020: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.020: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.020: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.020: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.020: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.020: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.020: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.020: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.020: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.020: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.021: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.021: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.021: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.021: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.021: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.021: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.021: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.021: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.021: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.021: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.021: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.021: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.021: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.021: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.021: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.022: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.022: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.022: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.022: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.022: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.022: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.022: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.022: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.022: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.022: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.022: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.022: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.022: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.022: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.023: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.023: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.023: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.023: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.023: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.023: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.023: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.023: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.023: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.023: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.024: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.024: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.024: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.024: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.024: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.024: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.025: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.025: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.025: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.025: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.025: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.025: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.025: variance_after = 17
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.025: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.025: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.025: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.026: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.026: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.026: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.026: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.026: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.026: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.026: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.026: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.026: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.026: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.027: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.027: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.027: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.027: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.027: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.027: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.027: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.027: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.027: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.027: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.027: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.027: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.027: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.027: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.028: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.028: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.028: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.028: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.028: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.028: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.028: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.028: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.028: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.028: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.029: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.029: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.029: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.029: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.029: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.029: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.029: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.029: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.029: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.029: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.029: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.029: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.029: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.029: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.030: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.030: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.030: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.030: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.030: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.030: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.030: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.030: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.030: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.030: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.031: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.031: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.031: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.031: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.031: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.031: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.031: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.031: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.031: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.031: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.031: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.031: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.031: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.031: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.031: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.031: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.032: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.032: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.032: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.032: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.032: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.032: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.032: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.032: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.032: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.032: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.032: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.032: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.032: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.032: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.033: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.033: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.033: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.033: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.033: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.033: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.033: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.033: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.033: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.033: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.034: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.034: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.034: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.034: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.034: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.034: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.034: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.034: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.034: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.034: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.034: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.034: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.034: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.034: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.035: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.035: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.035: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.035: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.035: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.035: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.035: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.035: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.035: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.035: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.036: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.036: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.036: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.036: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.036: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.036: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.036: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.036: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.036: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.036: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.036: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.036: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.036: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.036: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.037: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.037: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.037: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.037: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.037: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.037: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.037: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.037: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.037: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.037: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.038: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.038: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.038: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.038: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.038: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.038: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.038: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.038: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.038: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.038: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.038: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.038: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.038: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.038: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.039: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.039: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.039: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.039: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.039: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.039: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.039: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.039: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.039: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.039: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.040: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.040: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.040: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.040: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.040: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.040: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.040: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.040: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.040: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.040: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.040: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.040: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.040: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.040: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.040: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.040: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.041: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.041: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.041: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.041: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.041: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.041: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.041: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.041: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.041: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.041: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.041: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.041: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.041: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.041: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.042: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.042: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.042: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.042: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.042: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.042: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.042: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.042: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.042: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.042: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.043: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.043: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.043: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.043: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.043: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.043: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.043: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.043: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.043: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.043: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.043: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.043: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.043: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.043: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.044: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.044: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.044: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.044: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.044: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.044: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.044: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.044: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.044: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.044: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.045: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.045: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.045: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.045: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.045: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.045: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.045: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.045: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.045: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.045: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.045: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.045: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.045: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.045: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.045: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.046: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.046: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.046: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.046: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.046: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.046: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.046: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.046: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.046: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.046: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.046: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.046: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.046: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.046: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.046: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.047: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.047: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.047: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.047: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.047: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.047: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.047: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.047: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.047: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.047: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.047: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.047: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.047: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.047: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.047: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.047: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.048: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.048: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.048: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.048: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.048: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.048: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.048: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.048: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.048: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.048: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.048: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.048: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.049: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.049: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.049: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.049: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.049: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.049: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.049: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.049: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.049: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.049: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.049: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.049: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.049: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.049: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.050: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.050: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.050: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.050: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.050: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.050: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.050: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.050: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.050: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.050: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.050: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.050: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.050: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.050: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.050: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.050: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.051: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.051: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.051: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.051: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.051: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.051: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.051: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.051: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.051: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.051: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.051: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.051: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.051: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.051: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.052: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.052: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.052: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.052: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.052: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.052: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.052: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.052: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.053: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.053: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.053: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.053: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.053: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.053: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.053: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.053: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.053: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.053: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.054: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.054: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.054: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.054: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.054: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.054: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.054: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.054: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.054: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.054: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.054: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.054: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.054: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.054: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.055: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.055: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.055: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.055: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.055: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.055: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.055: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.055: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.055: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.055: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.056: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.056: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.056: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.056: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.056: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.056: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.056: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.056: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.056: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.056: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.056: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.057: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.057: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.057: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.057: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.057: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.057: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.057: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.058: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.058: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.058: variance_after = 17
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.058: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.058: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.058: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.058: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.058: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.058: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.058: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.058: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.058: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.058: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.058: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.059: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.059: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.059: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.059: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.059: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.059: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.059: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.059: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.059: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.059: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.060: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.060: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.060: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.060: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.060: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.060: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.060: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.060: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.060: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.061: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.061: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.061: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.061: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.061: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.061: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.061: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.061: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.061: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.061: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.061: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.061: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.061: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.061: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.061: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.062: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.062: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.062: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.062: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.062: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.062: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.062: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.062: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.062: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.062: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.062: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.062: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.062: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.062: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.063: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.063: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.063: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.063: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.063: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.063: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.063: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.063: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.063: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.064: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.064: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.064: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.064: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.064: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.064: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.064: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.064: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.064: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.064: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.064: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.064: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.064: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.064: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.064: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.065: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.065: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.065: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.065: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.065: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.065: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.065: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.065: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.065: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.065: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.066: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.066: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.066: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.066: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.066: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.066: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.066: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.066: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.066: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.066: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.066: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.066: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.066: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.066: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.067: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.067: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.067: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.067: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.067: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.067: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.067: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.067: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.067: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.067: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.068: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.068: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.068: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.068: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.068: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.068: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.068: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.068: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.068: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.068: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.068: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.068: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.068: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.068: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.069: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.069: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.069: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.069: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.069: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.069: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.069: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.069: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.069: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.069: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.069: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.069: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.069: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.069: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.069: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.069: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.070: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.070: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.070: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.070: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.070: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.070: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.070: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.070: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.071: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.071: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.071: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.071: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.071: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.071: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.071: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.071: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.071: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.071: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.071: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.071: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.071: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.071: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.071: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.071: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.072: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.072: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.072: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.072: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.072: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.072: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.072: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.072: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.072: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.072: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.073: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.073: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.073: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.073: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.073: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.073: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.073: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.073: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.073: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.073: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.073: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.073: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.073: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.073: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.073: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.073: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.074: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.074: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.074: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.074: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.074: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.074: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.074: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.074: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.074: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.074: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.074: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.074: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.074: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.074: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.075: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.075: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.075: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.075: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.075: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.075: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.075: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.075: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.075: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.075: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.076: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.076: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.076: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.076: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.076: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.076: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.076: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.076: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.076: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.076: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.076: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.076: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.076: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.076: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.077: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.077: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.077: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.077: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.077: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.077: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.077: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.077: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.077: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.077: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.078: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.078: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.078: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.078: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.078: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.078: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.078: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.078: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.078: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.078: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.078: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.078: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.078: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.078: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.079: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.079: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.079: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.079: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.079: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.079: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.079: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.079: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.079: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.079: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.079: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.079: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.079: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.079: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.079: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.079: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.080: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.080: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.080: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.080: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.080: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.080: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.080: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.080: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.080: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.080: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.081: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.081: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.081: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.081: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.081: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.081: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.081: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.081: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.081: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.081: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.081: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.081: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.081: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.081: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.082: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.082: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.082: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.082: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.082: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.082: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.082: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.082: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.082: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.082: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.083: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.083: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.083: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.083: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.083: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.083: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.083: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.083: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.083: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.083: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.083: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.083: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.083: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.083: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.083: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.083: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.084: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.084: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.084: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.084: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.084: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.084: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.084: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.084: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.084: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.084: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.084: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.084: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.084: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.084: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.085: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.085: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.085: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.085: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.085: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.085: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.085: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.085: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.085: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.085: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.086: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.086: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.086: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.086: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.086: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.086: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.086: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.086: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.086: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.086: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.086: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.086: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.086: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.086: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.087: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.087: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.087: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.087: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.087: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.087: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.087: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.087: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.087: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.087: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.088: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.088: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.088: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.088: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.088: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.088: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.088: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.088: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.088: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.088: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.088: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.088: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.088: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.088: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.089: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.089: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.089: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.089: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.089: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.089: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.089: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.089: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.089: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.089: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.090: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.090: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.090: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.090: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.090: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.090: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.090: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.090: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.090: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.090: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.090: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.090: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.090: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.090: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.091: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.091: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.091: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.091: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.091: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.091: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.091: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.091: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.091: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.091: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.092: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.092: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.092: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.092: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.092: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.092: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.092: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.092: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.092: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.092: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.092: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.092: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.092: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.092: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.093: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.093: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.093: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.093: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.093: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.093: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.093: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.093: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.093: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.093: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.094: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.094: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.094: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.094: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.094: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.094: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.094: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.094: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.094: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.094: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.094: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.094: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.094: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.094: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.094: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.094: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.095: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.095: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.095: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.095: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.095: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.095: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.095: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.095: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.095: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.095: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.095: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.096: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.096: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.096: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.096: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.096: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.096: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.096: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.096: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.096: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.097: variance_after = 17
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.097: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.097: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.097: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.097: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.097: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.097: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.097: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.097: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.097: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.097: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.097: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.098: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.098: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.098: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.098: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.098: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.098: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.098: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.098: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.098: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.098: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.098: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.098: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.098: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.098: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.098: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.098: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.099: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.099: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.099: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.099: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.099: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.099: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.099: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.099: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.099: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.099: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.100: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.100: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.100: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.100: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.100: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.100: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.100: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.100: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.100: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.100: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.100: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.100: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.100: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.100: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.101: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.101: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.101: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.101: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.101: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.101: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.101: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.101: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.101: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.101: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.101: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.101: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.101: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.101: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.101: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.101: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.102: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.102: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.102: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.102: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.102: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.102: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.102: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.102: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.102: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.102: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.103: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.103: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.103: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.103: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.103: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.103: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.103: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.103: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.103: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.103: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.103: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.103: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.103: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.103: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.103: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.103: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.104: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.104: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.104: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.104: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.104: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.104: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.104: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.104: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.104: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.104: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.104: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.104: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.104: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.104: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.105: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.105: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.105: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.105: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.105: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.105: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.105: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.105: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.105: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.105: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.106: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.106: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.106: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.106: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.106: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.106: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.106: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.106: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.106: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.106: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.106: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.106: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.106: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.106: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.107: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.107: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.107: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.107: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.107: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.107: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.107: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.107: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.107: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.107: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.107: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.107: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.107: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.107: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.107: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.107: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.108: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.108: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.108: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.108: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.108: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.108: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.108: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.108: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.108: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.108: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.109: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.109: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.109: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.109: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.109: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.109: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.109: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.109: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.109: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.109: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.109: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.109: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.109: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.109: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.109: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.109: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.109: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.109: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.109: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.109: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.109: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.109: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.110: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.110: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.110: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.110: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.110: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.110: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.110: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.110: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.110: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.110: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.111: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.111: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.111: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.111: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.111: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.111: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.111: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.111: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.111: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.111: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.111: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.111: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.111: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.111: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.112: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.112: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.112: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.112: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.112: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.112: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.112: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.112: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.112: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.112: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.112: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.112: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.112: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.112: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.112: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.112: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.113: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.113: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.113: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.113: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.113: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.113: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.113: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.113: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.113: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.113: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.114: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.114: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.114: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.114: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.114: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.114: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.114: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.114: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.114: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.114: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.114: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.114: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.114: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.114: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.115: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.115: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.115: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.115: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.115: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.115: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.115: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.115: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.115: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.115: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.115: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.115: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.115: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.115: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.115: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.115: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.116: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.116: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.116: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.116: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.116: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.116: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.116: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.116: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.116: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.116: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.117: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.117: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.117: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.117: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.117: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.117: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.117: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.117: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.117: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.117: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.117: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.117: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.117: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.117: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.118: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.118: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.118: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.118: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.118: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.118: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.118: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.118: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.118: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.118: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.118: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.118: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.118: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.118: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.119: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.119: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.119: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.119: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.119: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.119: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.119: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.119: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.119: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.119: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.120: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.120: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.120: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.120: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.120: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.120: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.120: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.120: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.120: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.120: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.120: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.120: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.120: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.120: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.120: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.121: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.121: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.121: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.121: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.121: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.121: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.121: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.121: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.121: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.121: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.121: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.122: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.122: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.122: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.122: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.122: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.122: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.122: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.122: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.122: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.122: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.122: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.122: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.122: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.122: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.123: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.123: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.123: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.123: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.123: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.123: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.123: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.123: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.123: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.123: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.123: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.123: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.123: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.123: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.123: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.123: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.124: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.124: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.124: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.124: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.124: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.124: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.124: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.124: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.124: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.124: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.125: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.125: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.125: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.125: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.125: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.125: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.125: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.125: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.125: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.125: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.125: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.125: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.125: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.125: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.125: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.125: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.126: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.126: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.126: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.126: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.126: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.126: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.126: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.126: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.126: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.126: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.126: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.126: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.126: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.126: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.127: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.127: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.127: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.127: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.127: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.127: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.127: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.127: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.127: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.127: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.128: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.128: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.128: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.128: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.128: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.128: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.128: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.128: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.128: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.128: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.128: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.128: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.128: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.128: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.129: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.129: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.129: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.129: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.129: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.129: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.129: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.129: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.129: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.129: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.130: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.130: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.130: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.130: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.130: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.130: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.130: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.130: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.130: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.130: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.130: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.130: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.130: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.130: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.131: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.131: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.131: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.131: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.131: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.131: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.131: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.131: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.132: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.132: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.132: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.132: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.132: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.132: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.132: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.132: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.132: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.132: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.133: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.133: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.133: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.133: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.133: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.133: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.133: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.133: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.133: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.133: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.133: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.133: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.133: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.133: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.133: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.133: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.134: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.134: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.134: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.134: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.134: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.134: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.134: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.134: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.134: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.134: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.134: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.134: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.134: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.134: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.135: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.135: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.135: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.135: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.135: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.135: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.135: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.135: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.135: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.136: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.136: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.136: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.136: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.136: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.136: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.136: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.136: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.136: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.136: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.136: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.136: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.136: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.136: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.136: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.137: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.137: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.137: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.137: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.137: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.137: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.137: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.137: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.137: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.137: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.138: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.138: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.138: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.138: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.138: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.138: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.138: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.138: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.138: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.138: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.138: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.138: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.138: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.138: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.139: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.139: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.139: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.139: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.139: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.139: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.139: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.139: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.139: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.139: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.140: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.140: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.140: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.140: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.140: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.140: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.140: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.140: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.140: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.140: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.140: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.140: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.140: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.140: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.141: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.141: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.141: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.141: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.141: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.141: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.141: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.141: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.141: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.141: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.142: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.142: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.142: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.142: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.142: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.142: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.142: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.142: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.142: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.142: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.142: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.142: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.142: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.142: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.143: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.143: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.143: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.143: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.143: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.143: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.143: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.143: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.143: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.143: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.143: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.143: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.144: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.144: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.144: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.144: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.144: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.144: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.144: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.144: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.144: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.144: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.144: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.144: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.144: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.144: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.145: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.145: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.145: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.145: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.145: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.145: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.145: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.145: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.145: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.145: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.145: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.145: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.145: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.145: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.146: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.146: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.146: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.146: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.146: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.146: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.146: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.146: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.146: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.146: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.147: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.147: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.147: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.147: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.147: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.147: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.147: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.147: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.147: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.147: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.147: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.147: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.147: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.147: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.147: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.148: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.148: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.148: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.148: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.148: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.148: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.148: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.148: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.148: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.149: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.149: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.149: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.149: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.149: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.149: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.149: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.149: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.149: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.149: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.149: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.149: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.149: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.149: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.150: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.150: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.150: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.150: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.150: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.150: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.150: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.150: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.150: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.150: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.151: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.151: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.151: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.151: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.151: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.151: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.151: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.151: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.151: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.151: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.151: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.151: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.151: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.151: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.152: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.152: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.152: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.152: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.152: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.152: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.152: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.152: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.152: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.152: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.153: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.153: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.153: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.153: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.153: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.153: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.153: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.153: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.153: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.153: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.153: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.153: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.153: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.153: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.154: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.154: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.154: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.154: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.154: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.154: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.154: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.154: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.154: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.154: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.155: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.155: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.155: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.155: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.155: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.155: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.155: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.155: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.155: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.155: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.155: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.155: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.155: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.155: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.156: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.156: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.156: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.156: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.156: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.156: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.156: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.156: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.156: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.156: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.157: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.157: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.157: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.157: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.157: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.157: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.157: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.157: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.157: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.157: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.157: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.157: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.157: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.157: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.158: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.158: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.158: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.158: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.158: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.158: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.158: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.158: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.158: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.158: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.158: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.158: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.158: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.158: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.158: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.158: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.159: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.159: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.159: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.159: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.159: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.159: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.159: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.159: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.159: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.159: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.160: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.160: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.160: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.160: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.160: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.160: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.160: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.160: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.160: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.160: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.160: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.160: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.160: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.160: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.160: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.160: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.161: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.161: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.161: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.161: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.161: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.161: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.161: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.161: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.161: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.161: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.161: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.161: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.161: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.161: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.162: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.162: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.162: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.162: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.162: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.162: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.162: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.162: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.162: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.162: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.163: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.163: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.163: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.163: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.163: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.163: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.163: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.163: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.163: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.163: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.163: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.163: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.163: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.163: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.163: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.164: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.164: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.164: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.164: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.164: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.164: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.164: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.164: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.164: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.164: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.164: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.164: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.164: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.164: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.164: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.165: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.165: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.165: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.165: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.165: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.165: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.165: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.165: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.165: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.165: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.166: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.166: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.166: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.166: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.166: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.166: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.166: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.166: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.166: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.166: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.166: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.166: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.166: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.166: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.167: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.167: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.167: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.167: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.167: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.167: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.167: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.167: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.167: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.167: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.168: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.168: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.168: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.168: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.168: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.168: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.168: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.168: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.168: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.168: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.168: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.168: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.168: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.168: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.169: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.169: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.169: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.169: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.169: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.169: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.169: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.169: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.169: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.169: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.170: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.170: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.170: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.170: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.170: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.170: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.170: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.170: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.170: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.170: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.170: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.170: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.170: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.170: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.171: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.171: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.171: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.171: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.171: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.171: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.171: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.171: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.171: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.171: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.171: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.171: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.171: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.171: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.171: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.171: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.172: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.172: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.172: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.172: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.172: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.172: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.172: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.172: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.172: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.172: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.172: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.172: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.172: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.172: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.172: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.172: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.173: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.173: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.173: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.173: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.173: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.173: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.173: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.173: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.173: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.173: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.174: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.174: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.174: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.174: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.174: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.174: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.174: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.174: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.174: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.174: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.174: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.174: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.174: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.174: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.174: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.175: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.175: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.175: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.175: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.175: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.175: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.175: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.175: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.175: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.175: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.175: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.175: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.175: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.175: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.175: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.176: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.176: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.176: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.176: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.176: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.176: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.176: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.176: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.176: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.176: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.176: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.176: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.176: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.176: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.176: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.176: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.177: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.177: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.177: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.177: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.177: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.177: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.177: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.177: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.177: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.177: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.178: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.178: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.178: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.178: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.178: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.178: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.178: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.178: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.178: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.178: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.178: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.178: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.178: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.178: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.178: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.178: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.179: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.179: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.179: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.179: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.179: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.179: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.179: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.179: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.179: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.179: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.179: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.179: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.179: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.179: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.180: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.180: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.180: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.180: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.180: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.180: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.180: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.180: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.180: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.180: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.181: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.181: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.181: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.181: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.181: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.181: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.181: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.181: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.181: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.181: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.181: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.181: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.181: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.181: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.182: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.182: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.182: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.182: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.182: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.182: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.182: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.182: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.182: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.182: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.183: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.183: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.183: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.183: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.183: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.183: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.183: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.183: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.183: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.183: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.183: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.183: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.183: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.183: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.184: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.184: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.184: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.184: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.184: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.184: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.184: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.184: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.184: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.184: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.185: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.185: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.185: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.185: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.185: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.185: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.185: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.185: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.185: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.185: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.185: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.185: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.185: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.185: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.186: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.186: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.186: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.186: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.186: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.186: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.186: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.186: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.186: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.186: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.187: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.187: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.187: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.187: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.187: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.187: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.187: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.187: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.187: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.187: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.187: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.187: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.187: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.187: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.188: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.188: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.188: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.188: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.188: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.188: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.188: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.188: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.188: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.188: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.188: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.188: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.188: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.189: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.189: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.189: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.189: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.189: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.189: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.189: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.190: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.190: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.190: variance_after = 20
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.190: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.190: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.190: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.190: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.190: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.190: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.190: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.190: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.190: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.190: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.190: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.190: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.190: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.191: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.191: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.191: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.191: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.191: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.191: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.191: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.191: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.192: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.192: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.192: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.192: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.192: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.192: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.192: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.192: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.192: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.192: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.192: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.192: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.192: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.192: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.192: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.192: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.193: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.193: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.193: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.193: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.193: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.193: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.193: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.193: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.193: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.193: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.193: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.193: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.193: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.193: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.193: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.193: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.194: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.194: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.194: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.194: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.194: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.194: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.194: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.194: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.194: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.194: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.194: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.194: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.194: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.194: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.195: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.195: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.195: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.195: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.195: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.195: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.195: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.195: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.195: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.195: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.196: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.196: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.196: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.196: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.196: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.196: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.196: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.196: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.196: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.196: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.196: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.196: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.196: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.196: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.196: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.196: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.197: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.197: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.197: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.197: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.197: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.197: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.197: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.197: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.197: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.197: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.197: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.197: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.197: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.197: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.197: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.197: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.198: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.198: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.198: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.198: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.198: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.198: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.198: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.198: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.198: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.198: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.198: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.198: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.198: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.198: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.198: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.198: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.199: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.199: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.199: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.199: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.199: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.199: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.199: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.199: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.199: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.199: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.199: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.199: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.199: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.199: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.199: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.199: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.200: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.200: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.200: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.200: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.200: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.200: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.200: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.200: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.200: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.200: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.200: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.200: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.200: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.200: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.201: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.201: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.201: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.201: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.201: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.201: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.201: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.201: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.201: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.201: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.201: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.201: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.201: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.201: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.201: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.201: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.202: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.202: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.202: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.202: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.202: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.202: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.202: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.202: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.202: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.202: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.203: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.203: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.203: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.203: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.203: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.203: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.203: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.203: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.203: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.203: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.203: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.203: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.203: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.203: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.204: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.204: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.204: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.204: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.204: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.204: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.204: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.204: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.204: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.204: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.205: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.205: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.205: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.205: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.205: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.205: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.205: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.205: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.205: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.205: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.205: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.205: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.205: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.205: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.206: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.206: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.206: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.206: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.206: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.206: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.206: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.206: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.206: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.206: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.207: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.207: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.207: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.207: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.207: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.207: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.207: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.207: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.207: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.207: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.207: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.207: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.207: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.207: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.207: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.207: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.208: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.208: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.208: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.208: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.208: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.208: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.208: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.208: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.208: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.208: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.208: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.208: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.208: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.208: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.209: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.209: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.209: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.209: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.209: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.209: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.209: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.209: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.209: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.209: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.210: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.210: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.210: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.210: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.210: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.210: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.210: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.210: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.210: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.210: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.210: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.210: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.210: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.210: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.210: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.210: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.211: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.211: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.211: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.211: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.211: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.211: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.211: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.211: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.211: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.211: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.211: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.211: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.211: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.211: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.212: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.212: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.212: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.212: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.212: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.212: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.212: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.212: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.212: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.212: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.213: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.213: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.213: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.213: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.213: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.213: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.213: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.213: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.213: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.213: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.213: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.213: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.213: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.213: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.213: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.213: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.214: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.214: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.214: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.214: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.214: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.214: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.214: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.214: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.214: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.214: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.214: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.214: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.214: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.214: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.215: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.215: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.215: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.215: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.215: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.215: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.215: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.215: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.215: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.215: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.216: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.216: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.216: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.216: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.216: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.216: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.216: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.216: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.216: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.216: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.216: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.216: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.216: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.216: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.217: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.217: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.217: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.217: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.217: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.217: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.217: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.217: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.217: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.217: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.217: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.217: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.218: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.218: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.218: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.218: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.218: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.218: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.218: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.218: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.218: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.218: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.218: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.218: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.218: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.218: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.219: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.219: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.219: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.219: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.219: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.219: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.219: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.219: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.219: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.219: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.219: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.219: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.219: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.219: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.220: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.220: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.220: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.220: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.220: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.220: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.220: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.220: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.220: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.220: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.221: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.221: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.221: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.221: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.221: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.221: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.221: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.221: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.221: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.221: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.221: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.221: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.221: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.221: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.222: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.222: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.222: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.222: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.222: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.222: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.222: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.222: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.222: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.222: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.223: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.223: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.223: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.223: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.223: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.223: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.223: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.223: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.223: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.223: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.223: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.223: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.223: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.223: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.224: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.224: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.224: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.224: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.224: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.224: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.224: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.224: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.224: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.224: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.225: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.225: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.225: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.225: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.225: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.225: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.225: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.225: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.225: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.225: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.225: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.225: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.225: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.225: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.226: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.226: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.226: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.226: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.226: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.226: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.226: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.226: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.226: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.226: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.227: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.227: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.227: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.227: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.227: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.227: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.227: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.227: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.227: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.227: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.227: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.227: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.227: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.227: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.227: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.227: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.228: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.228: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.228: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.228: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.228: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.228: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.228: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.228: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.228: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.228: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.228: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.228: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.228: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.228: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.229: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.229: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.229: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.229: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.229: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.229: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.229: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.229: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.229: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.229: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.230: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.230: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.230: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.230: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.230: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.230: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.230: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.230: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.230: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.230: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.230: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.230: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.230: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.230: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.231: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.231: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.231: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.231: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.231: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.231: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.231: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.231: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.231: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.231: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.232: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.232: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.232: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.232: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.232: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.232: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.232: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.232: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.232: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.232: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.232: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.232: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.232: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.232: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.232: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.233: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.233: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.233: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.233: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.233: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.233: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.233: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.233: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.233: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.234: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.234: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.234: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.234: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.234: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.234: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.234: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.234: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.234: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.234: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.234: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.234: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.234: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.234: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.234: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.235: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.235: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.235: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.235: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.235: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.235: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.235: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.235: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.235: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.235: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.235: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.235: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.235: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.235: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.235: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.236: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.236: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.236: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.236: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.236: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.236: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.236: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.237: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.237: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.237: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.237: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.237: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.237: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.237: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.237: variance_after = 17
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.237: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.237: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.237: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.238: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.238: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.238: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.238: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.238: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.238: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.238: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.238: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.238: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.238: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.239: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.239: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.239: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.239: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.239: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.239: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.239: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.239: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.240: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.240: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.240: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.240: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.240: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.240: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.240: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.240: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.240: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.240: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.240: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.240: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.240: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.240: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.241: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.241: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.241: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.241: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.241: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.241: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.241: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.241: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.241: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.241: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.242: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.242: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.242: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.242: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.242: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.242: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.242: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.242: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.242: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.242: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.242: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.242: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.242: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.242: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.243: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.243: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.243: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.243: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.243: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.243: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.243: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.243: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.243: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.243: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.243: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.243: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.243: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.243: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.243: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.243: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.244: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.244: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.244: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.244: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.244: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.244: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.244: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.244: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.244: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.244: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.245: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.245: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.245: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.245: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.245: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.245: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.245: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.245: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.245: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.245: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.245: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.245: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.245: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.245: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.246: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.246: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.246: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.246: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.246: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.246: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.246: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.246: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.246: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.246: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.247: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.247: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.247: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.247: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.247: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.247: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.247: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.247: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.247: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.247: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.247: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.247: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.247: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.247: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.248: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.248: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.248: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.248: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.248: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.248: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.248: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.248: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.248: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.248: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.249: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.249: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.249: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.249: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.249: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.249: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.249: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.249: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.249: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.249: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.249: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.249: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.249: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.249: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.250: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.250: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.250: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.250: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.250: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.250: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.250: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.250: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.250: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.250: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.251: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.251: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.251: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.251: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.251: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.251: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.251: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.251: Receiving 64 bytes
173s Executing: libfprint-2/driver-vfs7552.test
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.252: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.252: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.252: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.252: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.252: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.252: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.252: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.252: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.252: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.252: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.252: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.252: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.252: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.252: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.253: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.253: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.253: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.253: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.253: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.253: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.253: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.253: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.253: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.253: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.254: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.254: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.254: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.254: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.254: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.254: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.254: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.254: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.254: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.254: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.254: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.254: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.254: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.254: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.255: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.255: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.255: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.255: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.255: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.255: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.255: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.255: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.256: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.256: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.256: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.256: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.256: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.256: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.256: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.256: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.256: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.256: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.256: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.256: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.256: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.256: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.256: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.256: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.257: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.257: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.257: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.257: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.257: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.257: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.257: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.257: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.257: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.257: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.258: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.258: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.258: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.258: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.258: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.258: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.258: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.258: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.258: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.258: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.258: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.258: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.258: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.258: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.259: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.259: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.259: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.259: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.259: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.259: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.259: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.259: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.259: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.259: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.260: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.260: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.260: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.260: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.260: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.260: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.260: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.260: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.260: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.260: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.260: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.260: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.260: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.260: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.261: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.261: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.261: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.261: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.261: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.261: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.261: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.261: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.261: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.261: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.262: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.262: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.262: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.262: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.262: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.262: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.262: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.262: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.262: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.262: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.262: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.262: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.262: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.262: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.262: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.262: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.263: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.263: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.263: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.263: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.263: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.263: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.263: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.263: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.263: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.263: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.263: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.263: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.263: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.263: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.264: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.264: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.264: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.264: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.264: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.264: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.264: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.264: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.264: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.264: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.264: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.265: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.265: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.265: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.265: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.265: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.265: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.265: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.265: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.265: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.265: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.265: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.265: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.265: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.265: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.265: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.266: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.266: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.266: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.266: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.266: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.266: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.266: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.266: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.266: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.266: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.266: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.266: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.266: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.266: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.266: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.266: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.267: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.267: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.267: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.267: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.267: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.267: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.267: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.267: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.267: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.267: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.267: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.267: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.267: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.267: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.267: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.267: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.268: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.268: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.268: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.268: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.268: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.268: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.268: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.268: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.268: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.268: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.268: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.268: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.268: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.268: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.269: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.269: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.269: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.269: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.269: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.269: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.269: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.269: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.269: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.269: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.270: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.270: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.270: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.270: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.270: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.270: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.270: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.270: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.270: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.270: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.271: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.271: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.271: variance_after = 17
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.271: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.271: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.271: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.271: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.271: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.271: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.271: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.271: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.271: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.271: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.271: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.272: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.272: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.272: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.272: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.272: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.272: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.272: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.272: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.272: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.272: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.272: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.272: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.272: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.272: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.272: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.272: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.273: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.273: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.273: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.273: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.273: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.273: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.273: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.273: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.273: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.273: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.274: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.274: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.274: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.274: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.274: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.274: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.274: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.274: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.274: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.274: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.274: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.274: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.274: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.274: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.274: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.274: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.275: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.275: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.275: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.275: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.275: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.275: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.275: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.275: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.275: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.275: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.275: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.275: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.275: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.275: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.275: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.275: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.276: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.276: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.276: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.276: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.276: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.276: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.276: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.276: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.276: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.276: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.276: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.276: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.276: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.276: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.276: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.276: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.277: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.277: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.277: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.277: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.277: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.277: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.277: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.277: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.277: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.277: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.277: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.277: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.277: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.277: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.277: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.277: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.278: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.278: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.278: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.278: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.278: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.278: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.278: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.278: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.278: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.278: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.278: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.278: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.278: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.278: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.278: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.278: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.279: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.279: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.279: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.279: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.279: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.279: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.279: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.279: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.279: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.279: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.279: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.279: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.279: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.279: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.279: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.279: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.280: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.280: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.280: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.280: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.280: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.280: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.280: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.280: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.280: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.280: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.280: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.280: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.280: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.280: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.280: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.281: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.281: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.281: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.281: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.281: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.281: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.281: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.281: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.281: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.281: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.281: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.281: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.281: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.281: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.281: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.282: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.282: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.282: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.282: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.282: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.282: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.282: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.282: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.282: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.282: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.282: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.282: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.282: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.282: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.282: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.282: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.283: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.283: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.283: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.283: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.283: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.283: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.283: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.283: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.283: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.283: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.283: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.283: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.283: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.283: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.283: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.283: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.284: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.284: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.284: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.284: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.284: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.284: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.284: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.284: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.284: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.284: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.285: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.285: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.285: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.285: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.285: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.285: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.285: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.285: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.285: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.285: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.285: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.285: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.285: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.285: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.285: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.285: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.286: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.286: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.286: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.286: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.286: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.286: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.286: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.286: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.286: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.286: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.286: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.286: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.286: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.286: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.286: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.286: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.286: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.286: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.286: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.286: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.286: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.286: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.287: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.287: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.287: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.287: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.287: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.287: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.287: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.287: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.287: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.287: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.288: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.288: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.288: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.288: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.288: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.288: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.288: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.288: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.288: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.288: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.288: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.288: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.288: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.288: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.288: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.288: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.289: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.289: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.289: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.289: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.289: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.289: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.289: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.289: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.289: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.289: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.289: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.289: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.289: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.289: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.289: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.289: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.290: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.290: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.290: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.290: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.290: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.290: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.290: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.290: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.290: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.290: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.290: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.290: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.290: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.290: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.290: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.290: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.291: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.291: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.291: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.291: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.291: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.291: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.291: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.291: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.291: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.291: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.291: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.291: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.291: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.291: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.292: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.292: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.292: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.292: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.292: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.292: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.292: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.292: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.292: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.292: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.292: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.292: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.292: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.292: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.292: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.292: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.293: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.293: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.293: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.293: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.293: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.293: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.293: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.293: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.293: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.293: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.293: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.293: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.293: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.293: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.293: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.293: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.294: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.294: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.294: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.294: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.294: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.294: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.294: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.294: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.294: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.294: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.295: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.295: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.295: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.295: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.295: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.295: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.295: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.295: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.295: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.295: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.295: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.295: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.295: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.295: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.296: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.296: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.296: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.296: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.296: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.296: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.296: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.297: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.297: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.297: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.297: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.297: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.297: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.297: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.297: variance_after = 17
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.297: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.297: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.297: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.297: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.297: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.298: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.298: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.298: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.298: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.298: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.298: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.298: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.298: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.298: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.298: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.298: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.298: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.298: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.298: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.299: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.299: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.299: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.299: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.299: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.299: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.299: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.299: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.299: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.299: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.299: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.299: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.299: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.299: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.299: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.299: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.300: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.300: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.300: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.300: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.300: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.300: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.300: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.300: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.300: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.300: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.300: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.300: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.300: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.300: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.300: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.300: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.301: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.301: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.301: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.301: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.301: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.301: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.301: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.301: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.301: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.301: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.302: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.302: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.302: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.302: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.302: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.302: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.302: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.302: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.302: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.302: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.302: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.302: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.302: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.302: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.303: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.303: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.303: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.303: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.303: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.303: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.303: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.303: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.303: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.303: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.303: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.303: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.303: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.303: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.303: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.303: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.304: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.304: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.304: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.304: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.304: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.304: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.304: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.304: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.304: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.304: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.305: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.305: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.305: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.305: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.305: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.305: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.305: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.305: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.305: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.305: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.305: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.305: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.305: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.305: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.306: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.306: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.306: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.306: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.306: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.306: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.306: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.306: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.306: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.306: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.306: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.306: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.306: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.306: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.306: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.306: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.307: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.307: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.307: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.307: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.307: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.307: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.307: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.307: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.307: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.307: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.307: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.307: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.307: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.307: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.307: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.307: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.308: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.308: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.308: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.308: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.308: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.308: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.308: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.308: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.308: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.308: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.308: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.308: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.308: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.308: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.308: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.308: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.309: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.309: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.309: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.309: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.309: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.309: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.309: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.309: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.309: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.309: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.309: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.309: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.309: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.309: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.309: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.309: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.310: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.310: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.310: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.310: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.310: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.310: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.310: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.310: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.310: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.310: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.310: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.310: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.310: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.310: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.310: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.310: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.311: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.311: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.311: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.311: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.311: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.311: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.311: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.311: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.311: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.311: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.312: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.312: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.312: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.312: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.312: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.312: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.312: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.312: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.312: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.312: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.312: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.312: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.312: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.312: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.312: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.312: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.313: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.313: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.313: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.313: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.313: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.313: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.313: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.313: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.313: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.313: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.313: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.313: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.313: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.313: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.313: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.313: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.314: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.314: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.314: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.314: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.314: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.314: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.314: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.314: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.314: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.314: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.314: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.314: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.314: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.314: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.315: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.315: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.315: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.315: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.315: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.315: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.315: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.315: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.315: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.315: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.315: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.315: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.316: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.316: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.316: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.316: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.316: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.316: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.316: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.316: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.316: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.316: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.316: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.316: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.316: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.316: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.317: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.317: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.317: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.317: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.317: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.317: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.317: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.317: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.317: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.317: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.317: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.317: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.317: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.317: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.317: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.317: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.318: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.318: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.318: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.318: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.318: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.318: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.318: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.318: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.318: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.318: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.318: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.318: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.318: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.318: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.319: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.319: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.319: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.319: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.319: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.319: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.319: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.319: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.319: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.319: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.319: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.319: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.319: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.319: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.319: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.319: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.320: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.320: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.320: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.320: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.320: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.320: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.320: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.320: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.320: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.320: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.321: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.321: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.321: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.321: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.321: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.321: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.321: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.321: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.322: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.322: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.322: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.322: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.322: variance_after = 17
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.322: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.322: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.322: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.322: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.322: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.323: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.323: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.323: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.323: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.323: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.323: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.323: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.323: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.323: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.323: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.323: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.323: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.323: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.323: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.324: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.324: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.324: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.324: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.324: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.324: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.324: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.324: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.324: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.324: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.325: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.325: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.325: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.325: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.325: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.325: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.325: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.325: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.325: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.325: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.325: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.325: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.325: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.325: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.325: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.325: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.326: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.326: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.326: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.326: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.326: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.326: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.326: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.326: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.326: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.326: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.326: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.326: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.326: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.326: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.327: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.327: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.327: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.327: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.327: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.327: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.327: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.327: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.327: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.327: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.327: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.327: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.327: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.327: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.327: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.327: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.328: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.328: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.328: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.328: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.328: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.328: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.328: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.328: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.328: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.329: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.329: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.329: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.329: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.329: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.329: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.329: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.329: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.329: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.329: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.329: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.329: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.329: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.329: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.329: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.330: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.330: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.330: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.330: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.330: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.330: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.330: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.330: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.331: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.331: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.331: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.331: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.331: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.331: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.331: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.331: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.331: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.331: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.331: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.331: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.331: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.331: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.331: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.331: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.332: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.332: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.332: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.332: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.332: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.332: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.332: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.332: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.332: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.332: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.333: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.333: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.333: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.333: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.333: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.333: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.333: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.333: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.333: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.333: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.333: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.333: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.333: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.333: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.334: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.334: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.334: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.334: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.334: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.334: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.334: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.334: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.334: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.334: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.335: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.335: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.335: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.335: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.335: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.335: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.335: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.335: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.335: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.335: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.335: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.335: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.335: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.335: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.335: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.335: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.336: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.336: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.336: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.336: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.336: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.336: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.336: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.336: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.336: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.336: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.336: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.336: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.336: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.336: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.337: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.337: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.337: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.337: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.337: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.337: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.337: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.337: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.337: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.337: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.338: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.338: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.338: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.338: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.338: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.338: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.338: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.338: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.338: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.338: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.339: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.339: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.339: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.339: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.339: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.339: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.339: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.339: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.339: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.339: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.339: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.339: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.340: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.340: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.340: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.340: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.340: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.340: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.340: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.340: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.340: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.340: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.341: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.341: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.341: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.341: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.341: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.341: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.341: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.341: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.341: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.341: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.341: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.341: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.341: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.341: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.342: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.342: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.342: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.342: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.342: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.342: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.342: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.342: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.342: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.342: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.343: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.343: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.343: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.343: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.343: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.343: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.343: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.343: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.343: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.343: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.343: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.343: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.343: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.343: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.344: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.344: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.344: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.344: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.344: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.344: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.344: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.344: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.344: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.344: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.345: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.345: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.345: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.345: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.345: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.345: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.345: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.345: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.345: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.345: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.345: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.345: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.345: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.345: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.346: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.346: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.346: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.346: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.346: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.346: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.346: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.346: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.346: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.346: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.347: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.347: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.347: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.347: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.347: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.347: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.347: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.347: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.347: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.347: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.347: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.347: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.347: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.347: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.348: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.348: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.348: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.348: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.348: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.348: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.348: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.348: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.348: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.348: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.349: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.349: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.349: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.349: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.349: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.349: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.349: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.349: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.349: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.349: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.349: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.349: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.349: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.349: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.350: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.350: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.350: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.350: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.350: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.350: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.350: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.350: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.351: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.351: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.351: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.351: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.351: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.351: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.351: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.351: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.351: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.352: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.352: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.352: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.352: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.352: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.352: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.352: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.352: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.352: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.352: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.352: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.352: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.353: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.353: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.353: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.353: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.353: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.353: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.353: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.354: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.354: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.354: variance_after = 16
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.354: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.354: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.354: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.354: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.354: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.354: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.354: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.354: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.355: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.355: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.355: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.355: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.355: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.355: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.355: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.355: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.355: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.355: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.355: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.355: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.355: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.356: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.356: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.356: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.356: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.356: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.356: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.356: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.356: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.356: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.356: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.356: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.356: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.356: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.356: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.357: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.357: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.357: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.357: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.357: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.357: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.357: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.357: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.357: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.357: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.358: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.358: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.358: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.358: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.358: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.358: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.358: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.358: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.358: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.358: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.358: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.358: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.358: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.358: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.358: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.358: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.359: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.359: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.359: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.359: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.359: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.359: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.359: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.359: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.359: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.359: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.359: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.359: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.359: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.359: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.360: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.360: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.360: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.360: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.360: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.360: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.360: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.360: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.360: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.360: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.361: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.361: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.361: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.361: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.361: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.361: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.361: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.361: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.362: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.362: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.362: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.362: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.362: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.362: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.362: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.362: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.362: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.362: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.362: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.362: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.362: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.362: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.363: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.363: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.363: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.363: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.363: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.363: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.363: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.363: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.363: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.363: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.364: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.364: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.364: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.364: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.364: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.364: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.364: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.364: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.364: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.364: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.364: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.364: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.364: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.364: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.364: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.364: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.365: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.365: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.365: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.365: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.365: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.365: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.365: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.365: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.365: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.366: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.366: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.366: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.366: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.366: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.366: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.366: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.366: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.366: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.366: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.366: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.366: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.366: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.366: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.366: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.367: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.367: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.367: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.367: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.367: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.367: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.367: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.367: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.367: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.367: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.367: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.367: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.367: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.367: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.368: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.368: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.368: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.368: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.368: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.368: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.368: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.368: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.368: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.368: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.369: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.369: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.369: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.369: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.369: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.369: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.369: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.369: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.369: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.369: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.369: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.369: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.369: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.369: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.370: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.370: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.370: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.370: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.370: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.370: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.370: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.370: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.370: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.370: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.370: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.370: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.370: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.370: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.370: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.370: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.371: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.371: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.371: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.371: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.371: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.371: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.371: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.371: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.371: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.371: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.372: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.372: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.372: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.372: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.372: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.372: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.372: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.372: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.372: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.372: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.372: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.372: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.372: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.372: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.372: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.372: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.373: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.373: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.373: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.373: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.373: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.373: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.373: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.373: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.373: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.373: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.373: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.373: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.373: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.373: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.374: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.374: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.374: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.374: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.374: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.374: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.374: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.374: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.374: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.374: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.375: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.375: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.375: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.375: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.375: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.375: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.375: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.375: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.375: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.375: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.375: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.375: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.375: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.375: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.376: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.376: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.376: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.376: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.376: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.376: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.376: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.376: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.376: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.376: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.377: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.377: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.377: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.377: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.377: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.377: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.377: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.377: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.377: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.377: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.377: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.377: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.377: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.377: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.378: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.378: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.378: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.378: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.378: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.378: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.378: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.378: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.378: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.378: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.379: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.379: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.379: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.379: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.379: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.379: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.379: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.379: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.379: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.379: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.379: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.379: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.379: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.379: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.379: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.380: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.380: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.380: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.380: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.380: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.380: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.380: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.380: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.380: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.380: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.380: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.380: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.380: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.380: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.380: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.381: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.381: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.381: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.381: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.381: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.381: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.381: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.381: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.382: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.382: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.382: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.382: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.382: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.382: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.382: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.382: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.382: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.382: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.383: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.383: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.383: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.383: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.383: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.383: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.383: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.383: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.383: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.383: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.384: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.384: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.384: variance_after = 17
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.384: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.384: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.384: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.384: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.384: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.384: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.385: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.385: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.385: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.385: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.385: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.385: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.385: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.385: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.385: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.385: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.385: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.385: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.385: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.386: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.386: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.386: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.386: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.386: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.386: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.386: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.386: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.386: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.386: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.386: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.386: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.386: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.386: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.386: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.386: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.387: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.387: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.387: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.387: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.387: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.387: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.387: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.387: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.387: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.387: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.387: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.387: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.387: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.387: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.387: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.387: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.388: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.388: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.388: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.388: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.388: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.388: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.388: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.388: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.388: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.388: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.388: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.388: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.388: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.388: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.388: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.388: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.389: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.389: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.389: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.389: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.389: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.389: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.389: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.389: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.389: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.389: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.390: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.390: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.390: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.390: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.390: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.390: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.390: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.390: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.390: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.390: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.390: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.390: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.390: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.390: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.391: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.391: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.391: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.391: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.391: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.391: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.391: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.391: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.391: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.391: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.392: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.392: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.392: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.392: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.392: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.392: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.392: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.392: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.392: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.392: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.392: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.392: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.392: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.392: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.393: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.393: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.393: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.393: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.393: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.393: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.393: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.393: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.393: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.393: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.394: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.394: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.394: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.394: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.394: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.394: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.394: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.394: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.394: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.394: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.394: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.394: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.394: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.394: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.394: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.394: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.395: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.395: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.395: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.395: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.395: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.395: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.395: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.395: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.395: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.395: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.395: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.395: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.395: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.395: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.396: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.396: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.396: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.396: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.396: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.396: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.396: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.396: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.396: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.396: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.397: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.397: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.397: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.397: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.397: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.397: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.397: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.397: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.397: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.397: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.397: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.397: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.398: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.398: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.398: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.398: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.398: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.398: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.398: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.398: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.398: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.398: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.399: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.399: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.399: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.399: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.399: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.399: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.399: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.399: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.399: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.399: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.399: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.399: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.399: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.399: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.399: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.399: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.400: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.400: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.400: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.400: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.400: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.400: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.400: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.400: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.400: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.400: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.401: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.401: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.401: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.401: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.401: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.401: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.401: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.401: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.401: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.401: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.401: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.401: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.401: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.401: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.402: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.402: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.402: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.402: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.402: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.402: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.402: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.402: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.402: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.403: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.403: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.403: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.403: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.403: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.403: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.403: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.403: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.403: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.403: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.403: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.403: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.403: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.404: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.404: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.404: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.404: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.404: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.404: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.404: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.404: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.404: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.404: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.404: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.404: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.405: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.405: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.405: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.405: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.405: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.405: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.405: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.405: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.405: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.405: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.405: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.405: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.405: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.405: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.406: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.406: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.406: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.406: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.406: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.406: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.406: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.406: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.406: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.406: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.407: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.407: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.407: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.407: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.407: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.407: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.407: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.407: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.407: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.407: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.407: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.407: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.407: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.407: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.408: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.408: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.408: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.408: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.408: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.408: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.408: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.408: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.408: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.408: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.408: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.408: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.408: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.408: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.408: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.408: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.409: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.409: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.409: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.409: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.409: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.409: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.409: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.409: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.410: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.410: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.410: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.410: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.410: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.410: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.410: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.410: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.410: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.410: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.411: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.411: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.411: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.411: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.411: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.411: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.411: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.411: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.412: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.412: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.412: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.412: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.412: variance_after = 16
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.412: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.412: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.412: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.412: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.412: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.413: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.413: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.413: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.413: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.413: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.413: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.413: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.413: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.413: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.413: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.413: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.413: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.413: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.413: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.414: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.414: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.414: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.414: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.414: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.414: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.414: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.414: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.414: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.414: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.415: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.415: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.415: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.415: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.415: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.415: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.415: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.415: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.415: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.416: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.416: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.416: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.416: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.416: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.416: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.416: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.416: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.416: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.416: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.416: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.416: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.416: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.416: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.417: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.417: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.417: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.417: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.417: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.417: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.417: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.417: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.417: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.418: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.418: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.418: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.418: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.418: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.418: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.418: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.418: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.418: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.418: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.418: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.418: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.418: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.418: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.418: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.419: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.419: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.419: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.419: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.419: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.419: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.419: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.419: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.419: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.419: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.419: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.419: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.419: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.419: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.419: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.420: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.420: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.420: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.420: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.420: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.420: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.420: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.420: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.420: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.421: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.421: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.421: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.421: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.421: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.421: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.421: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.421: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.421: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.421: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.421: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.421: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.421: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.421: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.421: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.422: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.422: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.422: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.422: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.422: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.422: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.422: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.422: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.422: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.422: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.422: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.423: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.423: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.423: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.423: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.423: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.423: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.423: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.423: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.423: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.423: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.423: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.423: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.423: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.423: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.424: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.424: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.424: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.424: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.424: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.424: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.424: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.424: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.424: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.425: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.425: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.425: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.425: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.425: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.425: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.425: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.425: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.425: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.425: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.425: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.425: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.425: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.425: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.426: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.426: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.426: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.426: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.426: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.426: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.426: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.426: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.426: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.426: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.427: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.427: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.427: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.427: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.427: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.427: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.427: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.427: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.427: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.427: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.427: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.427: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.427: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.427: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.428: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.428: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.428: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.428: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.428: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.428: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.428: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.428: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.428: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.428: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.429: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.429: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.429: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.429: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.429: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.429: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.429: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.429: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.429: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.429: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.429: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.429: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.429: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.429: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.430: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.430: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.430: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.430: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.430: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.430: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.430: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.430: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.430: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.430: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.430: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.431: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.431: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.431: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.431: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.431: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.431: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.431: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.431: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.431: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.431: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.431: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.431: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.431: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.431: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.431: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.432: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.432: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.432: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.432: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.432: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.432: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.432: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.432: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.432: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.432: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.432: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.432: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.432: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.432: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.433: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.433: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.433: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.433: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.433: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.433: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.433: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.433: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.433: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.433: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.433: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.433: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.433: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.433: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.433: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.433: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.434: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.434: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.434: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.434: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.434: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.434: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.434: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.434: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.434: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.434: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.435: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.435: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.435: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.435: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.435: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.435: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.435: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.435: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.435: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.435: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.435: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.435: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.435: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.435: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.435: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.435: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.436: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.436: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.436: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.436: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.436: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.436: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.436: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.436: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.436: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.436: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.436: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.436: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.436: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.436: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.437: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.437: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.437: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.437: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.437: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.437: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.437: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.437: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.437: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.437: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.437: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.437: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.437: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.437: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.437: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.437: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.438: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.438: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.438: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.438: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.438: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.438: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.438: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.438: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.438: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.438: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.438: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.438: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.438: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.439: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.439: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.439: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.439: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.439: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.439: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.439: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.440: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.440: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.440: variance_after = 2168
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.440: [vfs7552] CAPTURE_NUM_STATES completed successfully
173s (process:2479): libfprint-device-DEBUG: 05:03:04.440: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
173s (process:2479): libfprint-image_device-DEBUG: 05:03:04.440: Image device reported finger status: on
173s (process:2479): libfprint-image_device-DEBUG: 05:03:04.440: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.490: changing to 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.490: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.490: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.490: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.490: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.490: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.490: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.490: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.490: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.490: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.490: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.490: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.491: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.491: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.491: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.491: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.491: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.492: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.492: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.492: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.492: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.492: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.492: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.492: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.493: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.493: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.493: variance_after = 2082
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.493: [vfs7552] CAPTURE_NUM_STATES completed successfully
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.493: Image captured
173s (process:2479): libfprint-image_device-DEBUG: 05:03:04.493: Image device captured an image
173s (process:2479): libfprint-image_device-DEBUG: 05:03:04.493: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
173s (process:2479): libfprint-device-DEBUG: 05:03:04.493: Device reported finger status change: FP_FINGER_STATUS_PRESENT
173s (process:2479): libfprint-image-DEBUG: 05:03:04.510: Minutiae scan completed in 0.017316 secs
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.543: changing to 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.543: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.543: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.543: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.543: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.543: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.544: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.544: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.544: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.544: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.544: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.544: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.544: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.544: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.544: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.544: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.544: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.544: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.544: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.545: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.545: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.545: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.545: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.545: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.545: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.545: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.545: variance_after = 2003
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.545: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.545: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.545: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.546: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.546: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.546: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.546: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.546: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.546: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.546: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.546: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.546: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.546: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.547: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.547: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.547: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.547: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.547: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.547: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.547: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.547: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.547: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.547: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.547: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.547: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.547: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.547: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.548: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.548: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.548: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.548: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.548: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.548: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.548: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.548: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.548: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.548: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.549: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.549: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.549: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.549: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.549: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.549: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.549: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.549: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.549: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.549: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.549: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.549: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.549: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.549: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.550: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.550: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.550: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.550: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.550: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.550: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.550: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.550: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.550: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.550: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.551: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.551: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.551: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.551: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.551: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.551: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.551: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.551: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.551: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.551: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.551: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.551: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.551: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.551: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.552: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.552: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.552: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.552: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.552: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.552: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.552: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.552: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.552: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.552: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.553: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.553: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.553: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.553: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.553: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.553: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.553: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.553: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.553: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.553: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.554: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.554: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.554: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.554: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.554: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.554: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.554: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.554: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.554: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.554: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.554: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.554: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.554: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.554: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.555: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.555: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.555: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.555: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.555: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.555: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.555: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.555: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.555: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.555: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.555: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.555: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.555: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.555: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.556: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.556: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.556: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.556: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.556: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.556: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.556: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.556: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.556: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.556: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.557: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.557: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.557: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.557: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.557: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.557: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.557: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.557: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.557: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.557: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.557: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.557: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.557: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.557: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.558: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.558: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.558: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.558: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.558: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.558: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.558: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.558: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.558: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.558: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.559: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.559: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.559: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.559: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.559: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.559: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.559: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.559: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.559: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.559: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.559: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.559: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.559: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.559: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.559: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.559: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.560: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.560: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.560: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.560: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.560: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.560: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.560: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.560: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.560: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.560: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.560: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.560: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.560: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.560: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.561: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.561: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.561: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.561: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.561: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.561: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.561: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.561: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.561: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.561: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.562: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.562: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.562: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.562: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.562: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.562: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.562: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.562: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.562: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.562: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.562: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.562: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.562: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.562: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.563: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.563: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.563: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.563: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.563: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.563: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.563: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.563: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.563: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.563: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.564: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.564: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.564: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.564: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.564: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.564: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.564: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.564: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.564: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.564: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.564: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.564: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.564: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.564: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.565: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.565: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.565: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.565: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.565: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.565: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.565: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.565: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.565: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.565: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.565: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.565: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.565: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.565: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.565: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.565: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.566: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.566: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.566: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.566: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.566: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.566: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.566: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.566: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.566: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.566: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.567: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.567: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.567: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.567: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.567: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.567: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.567: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.567: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.567: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.567: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.567: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.567: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.567: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.567: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.568: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.568: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.568: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.568: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.568: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.568: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.568: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.568: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.568: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.568: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.568: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.568: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.568: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.568: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.568: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.568: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.569: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.569: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.569: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.569: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.569: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.569: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.569: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.569: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.569: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.569: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.570: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.570: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.570: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.570: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.570: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.570: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.570: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.570: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.570: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.570: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.570: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.570: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.570: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.570: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.571: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.571: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.571: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.571: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.571: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.571: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.571: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.571: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.571: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.571: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.571: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.572: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.572: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.572: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.572: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.572: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.572: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.572: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.572: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.572: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.572: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.572: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.572: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.572: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.573: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.573: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.573: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.573: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.573: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.573: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.573: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.573: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.573: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.573: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.574: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.574: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.574: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.574: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.574: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.574: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.574: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.574: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.574: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.574: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.574: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.574: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.574: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.574: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.574: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.574: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.575: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.575: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.575: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.575: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.575: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.575: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.575: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.575: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.575: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.575: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.575: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.575: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.575: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.575: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.576: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.576: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.576: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.576: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.576: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.576: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.576: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.576: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.576: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.576: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.577: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.577: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.577: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.577: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.577: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.577: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.577: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.577: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.577: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.577: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.577: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.577: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.577: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.577: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.578: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.578: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.578: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.578: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.578: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.578: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.578: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.578: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.578: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.578: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.578: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.578: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.578: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.578: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.578: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.578: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.579: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.579: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.579: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.579: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.579: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.579: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.579: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.579: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.579: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.579: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.580: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.580: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.580: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.580: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.580: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.580: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.580: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.580: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.580: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.580: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.580: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.580: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.580: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.580: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.580: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.580: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.581: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.581: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.581: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.581: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.581: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.581: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.581: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.581: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.581: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.581: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.581: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.581: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.581: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.581: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.582: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.582: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.582: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.582: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.582: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.582: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.582: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.582: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.582: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.582: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.583: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.583: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.583: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.583: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.583: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.583: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.583: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.583: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.583: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.583: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.583: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.583: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.583: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.583: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.583: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.583: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.584: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.584: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.584: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.584: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.584: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.584: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.584: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.584: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.584: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.584: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.584: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.584: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.584: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.584: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.585: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.585: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.585: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.585: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.585: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.585: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.585: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.585: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.585: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.585: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.586: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.586: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.586: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.586: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.586: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.586: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.586: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.586: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.586: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.586: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.586: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.586: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.586: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.586: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.587: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.587: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.587: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.587: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.587: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.587: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.587: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.587: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.587: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.587: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.588: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.588: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.588: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.588: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.588: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.588: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.588: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.588: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.588: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.588: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.588: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.588: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.588: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.588: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.589: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.589: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.589: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.589: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.589: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.589: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.589: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.589: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.589: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.589: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.590: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.590: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.590: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.590: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.590: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.590: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.590: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.590: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.590: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.590: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.590: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.590: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.590: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.590: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.591: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.591: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.591: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.591: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.591: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.591: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.591: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.591: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.591: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.591: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.592: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.592: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.592: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.592: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.592: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.592: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.592: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.592: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.592: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.592: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.592: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.592: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.592: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.592: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.593: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.593: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.593: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.593: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.593: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.593: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.593: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.593: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.593: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.593: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.594: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.594: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.594: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.594: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.594: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.594: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.594: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.594: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.594: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.594: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.594: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.594: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.594: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.594: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.595: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.595: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.595: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.595: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.595: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.595: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.595: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.595: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.595: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.595: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.596: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.596: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.596: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.596: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.596: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.596: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.596: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.596: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.596: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.596: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.596: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.596: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.596: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.596: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.597: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.597: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.597: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.597: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.597: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.597: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.597: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.597: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.597: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.597: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.598: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.598: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.598: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.598: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.598: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.598: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.598: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.598: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.598: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.598: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.598: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.598: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.598: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.598: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.599: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.599: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.599: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.599: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.599: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.599: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.599: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.599: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.599: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.599: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.600: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.600: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.600: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.600: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.600: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.600: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.600: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.600: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.600: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.600: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.600: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.600: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.600: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.600: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.601: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.601: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.601: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.601: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.601: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.601: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.601: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.601: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.601: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.601: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.602: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.602: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.602: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.602: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.602: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.602: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.602: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.602: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.602: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.602: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.602: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.602: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.602: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.602: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.603: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.603: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.603: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.603: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.603: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.603: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.603: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.603: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.603: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.603: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.603: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.604: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.604: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.604: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.604: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.604: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.604: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.604: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.604: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.604: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.604: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.604: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.604: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.604: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.604: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.604: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.605: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.605: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.605: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.605: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.605: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.605: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.605: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.605: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.605: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.605: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.605: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.605: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.605: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.605: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.606: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.606: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.606: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.606: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.606: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.606: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.606: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.606: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.606: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.606: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.607: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.607: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.607: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.607: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.607: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.607: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.607: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.607: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.607: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.607: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.607: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.607: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.607: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.607: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.607: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.607: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.608: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.608: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.608: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.608: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.608: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.608: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.608: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.608: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.608: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.608: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.608: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.608: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.608: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.608: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.609: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.609: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.609: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.609: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.609: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.609: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.609: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.609: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.609: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.609: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.610: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.610: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.610: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.610: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.610: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.610: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.610: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.610: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.610: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.610: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.610: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.610: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.610: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.610: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.611: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.611: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.611: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.611: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.611: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.611: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.611: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.611: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.611: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.611: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.612: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.612: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.612: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.612: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.612: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.612: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.612: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.612: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.612: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.612: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.612: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.612: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.612: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.612: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.613: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.613: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.613: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.613: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.613: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.613: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.613: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.613: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.613: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.613: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.614: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.614: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.614: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.614: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.614: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.614: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.614: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.614: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.614: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.614: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.614: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.614: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.614: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.614: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.615: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.615: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.615: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.615: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.615: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.615: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.615: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.615: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.615: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.615: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.616: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.616: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.616: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.616: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.616: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.616: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.616: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.616: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.616: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.616: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.616: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.616: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.616: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.616: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.616: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.617: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.617: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.617: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.617: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.617: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.617: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.617: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.617: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.617: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.617: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.617: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.617: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.617: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.617: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.617: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.618: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.618: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.618: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.618: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.618: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.618: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.618: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.618: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.618: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.618: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.619: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.619: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.619: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.619: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.619: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.619: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.619: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.619: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.620: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.620: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.620: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.620: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.620: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.620: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.620: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.620: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.620: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.620: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.620: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.620: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.620: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.620: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.621: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.621: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.621: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.621: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.621: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.621: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.621: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.621: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.621: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.621: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.621: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.622: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.622: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.622: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.622: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.622: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.622: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.622: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.622: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.622: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.622: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.622: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.622: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.622: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.623: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.623: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.623: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.623: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.623: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.623: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.623: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.623: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.623: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.623: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.623: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.623: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.623: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.623: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.623: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.623: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.624: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.624: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.624: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.624: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.624: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.624: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.624: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.624: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.624: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.624: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.624: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.624: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.625: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.625: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.625: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.625: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.625: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.625: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.625: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.625: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.625: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.625: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.625: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.625: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.625: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.625: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.626: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.626: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.626: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.626: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.626: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.626: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.626: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.626: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.626: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.626: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.626: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.626: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.626: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.626: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.627: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.627: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.627: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.627: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.627: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.627: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.627: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.627: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.627: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.627: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.628: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.628: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.628: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.628: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.628: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.628: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.628: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.628: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.628: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.628: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.628: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.628: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.628: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.628: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.629: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.629: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.629: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.629: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.629: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.629: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.629: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.629: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.629: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.629: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.629: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.629: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.629: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.629: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.629: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.629: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.630: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.630: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.630: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.630: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.630: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.630: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.630: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.630: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.630: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.631: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.631: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.631: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.631: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.631: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.631: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.631: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.631: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.631: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.631: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.631: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.631: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.631: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.631: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.631: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.632: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.632: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.632: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.632: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.632: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.632: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.632: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.632: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.632: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.632: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.633: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.633: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.633: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.633: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.633: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.633: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.633: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.633: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.633: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.633: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.633: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.633: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.633: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.633: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.634: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.634: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.634: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.634: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.634: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.634: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.634: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.634: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.634: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.634: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.635: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.635: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.635: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.635: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.635: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.635: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.635: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.635: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.635: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.635: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.635: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.635: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.635: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.635: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.636: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.636: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.636: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.636: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.636: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.636: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.636: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.636: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.636: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.636: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.636: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.636: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.637: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.637: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.637: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.637: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.637: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.637: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.637: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.637: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.637: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.637: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.637: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.637: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.637: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.637: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.638: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.638: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.638: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.638: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.638: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.638: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.638: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.638: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.639: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.639: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.639: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.639: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.639: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.639: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.639: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.639: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.639: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.639: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.639: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.639: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.639: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.639: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.640: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.640: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.640: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.640: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.640: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.640: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.640: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.640: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.640: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.640: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.640: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.640: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.640: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.640: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.640: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.640: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.641: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.641: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.641: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.641: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.641: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.641: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.641: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.641: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.641: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.641: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.642: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.642: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.642: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.642: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.642: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.642: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.642: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.642: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.642: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.642: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.642: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.642: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.642: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.642: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.643: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.643: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.643: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.643: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.643: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.643: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.643: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.643: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.643: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.643: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.643: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.643: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.643: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.643: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.643: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.643: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.644: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.644: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.644: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.644: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.644: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.644: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.644: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.644: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.644: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.644: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.644: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.644: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.644: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.644: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.644: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.644: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.645: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.645: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.645: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.645: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.645: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.645: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.645: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.645: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.645: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.645: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.645: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.645: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.645: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.646: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.646: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.646: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.646: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.646: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.646: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.646: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.647: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.647: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.647: variance_after = 1737
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.647: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.647: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.647: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.647: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.647: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.647: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.647: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.647: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.647: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.647: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.647: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.647: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.647: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.648: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.648: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.648: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.648: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.648: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.648: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.648: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.648: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.648: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.648: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.648: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.648: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.648: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.648: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.648: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.649: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.649: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.649: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.649: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.649: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.649: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.649: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.649: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.649: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.649: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.649: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.649: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.649: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.649: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.649: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.650: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.650: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.650: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.650: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.650: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.650: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.650: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.650: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.650: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.650: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.651: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.651: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.651: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.651: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.651: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.651: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.651: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.651: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.651: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.651: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.651: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.651: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.651: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.651: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.652: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.652: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.652: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.652: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.652: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.652: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.652: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.652: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.652: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.652: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.652: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.652: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.652: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.652: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.652: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.652: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.653: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.653: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.653: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.653: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.653: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.653: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.653: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.653: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.653: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.653: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.653: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.653: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.653: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.653: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.653: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.653: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.654: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.654: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.654: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.654: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.654: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.654: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.654: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.654: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.654: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.654: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.655: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.655: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.655: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.655: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.655: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.655: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.655: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.655: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.655: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.655: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.655: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.655: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.655: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.655: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.656: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.656: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.656: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.656: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.656: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.656: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.656: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.656: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.656: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.656: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.657: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.657: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.657: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.657: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.657: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.657: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.657: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.657: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.657: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.657: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.657: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.657: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.657: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.657: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.657: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.657: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.658: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.658: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.658: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.658: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.658: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.658: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.658: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.658: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.658: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.658: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.658: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.658: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.658: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.658: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.658: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.658: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.659: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.659: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.659: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.659: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.659: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.659: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.659: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.659: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.659: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.659: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.659: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.659: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.659: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.659: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.659: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.659: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.660: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.660: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.660: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.660: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.660: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.660: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.660: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.660: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.660: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.660: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.660: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.660: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.660: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.660: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.661: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.661: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.661: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.661: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.661: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.661: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.661: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.661: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.661: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.661: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.662: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.662: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.662: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.662: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.662: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.662: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.662: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.662: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.662: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.662: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.662: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.662: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.662: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.662: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.662: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.662: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.663: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.663: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.663: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.663: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.663: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.663: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.663: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.663: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.663: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.663: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.663: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.663: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.663: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.663: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.664: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.664: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.664: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.664: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.664: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.664: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.664: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.664: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.664: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.664: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.665: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.665: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.665: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.665: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.665: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.665: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.665: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.665: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.665: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.665: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.665: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.665: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.665: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.665: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.665: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.665: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.666: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.666: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.666: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.666: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.666: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.666: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.666: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.666: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.666: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.666: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.666: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.666: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.666: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.666: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.667: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.667: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.667: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.667: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.667: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.667: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.667: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.667: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.667: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.667: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.668: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.668: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.668: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.668: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.668: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.668: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.668: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.668: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.668: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.668: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.668: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.668: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.668: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.668: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.669: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.669: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.669: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.669: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.669: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.669: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.669: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.669: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.669: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.669: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.669: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.669: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.669: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.669: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.669: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.669: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.670: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.670: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.670: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.670: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.670: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.670: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.670: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.670: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.670: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.670: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.671: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.671: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.671: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.671: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.671: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.671: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.671: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.671: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.671: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.671: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.671: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.671: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.671: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.671: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.672: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.672: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.672: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.672: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.672: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.672: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.672: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.672: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.672: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.672: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.673: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.673: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.673: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.673: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.673: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.673: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.673: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.673: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.673: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.673: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.673: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.673: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.673: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.673: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.673: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.673: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.674: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.674: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.674: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.674: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.674: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.674: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.674: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.674: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.674: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.674: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.674: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.674: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.674: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.674: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.675: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.675: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.675: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.675: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.675: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.675: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.675: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.675: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.675: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.675: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.675: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.675: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.675: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.675: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.675: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.675: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.676: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.676: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.676: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.676: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.676: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.676: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.676: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.676: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.676: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.676: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.677: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.677: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.677: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.677: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.677: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.677: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.677: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.677: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.677: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.677: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.677: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.677: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.677: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.677: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.677: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.677: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.678: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.678: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.678: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.678: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.678: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.678: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.678: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.678: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.678: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.678: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.678: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.678: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.678: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.678: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.679: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.679: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.679: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.679: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.679: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.679: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.679: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.679: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.679: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.679: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.680: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.680: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.680: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.680: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.680: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.680: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.680: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.680: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.680: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.680: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.680: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.680: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.680: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.680: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.680: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.680: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.681: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.681: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.681: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.681: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.681: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.681: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.681: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.681: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.681: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.681: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.681: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.681: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.681: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.681: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.682: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.682: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.682: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.682: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.682: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.682: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.682: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.682: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.682: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.682: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.683: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.683: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.683: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.683: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.683: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.683: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.683: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.683: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.683: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.683: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.683: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.683: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.683: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.683: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.683: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.683: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.684: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.684: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.684: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.684: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.684: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.684: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.684: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.684: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.684: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.684: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.684: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.684: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.684: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.684: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.685: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.685: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.685: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.685: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.685: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.685: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.685: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.685: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.685: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.685: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.685: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.685: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.685: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.685: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.685: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.685: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.686: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.686: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.686: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.686: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.686: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.686: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.686: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.686: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.686: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.686: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.687: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.687: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.687: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.687: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.687: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.687: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.687: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.687: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.687: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.687: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.687: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.687: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.687: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.687: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.688: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.688: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.688: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.688: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.688: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.688: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.688: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.688: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.688: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.688: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.688: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.688: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.688: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.688: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.688: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.688: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.689: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.689: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.689: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.689: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.689: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.689: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.689: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.689: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.689: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.689: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.690: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.690: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.690: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.690: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.690: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.690: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.690: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.690: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.690: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.690: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.690: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.690: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.690: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.690: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.691: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.691: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.691: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.691: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.691: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.691: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.691: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.691: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.691: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.691: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.692: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.692: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.692: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.692: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.692: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.692: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.692: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.692: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.692: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.692: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.692: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.692: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.692: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.692: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.693: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.693: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.693: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.693: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.693: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.693: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.693: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.693: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.693: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.693: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.694: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.694: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.694: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.694: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.694: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.694: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.694: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.694: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.694: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.694: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.694: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.694: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.694: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.694: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.695: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.695: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.695: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.695: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.695: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.695: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.695: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.695: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.695: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.695: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.696: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.696: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.696: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.696: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.696: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.696: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.696: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.696: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.696: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.696: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.696: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.696: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.696: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.696: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.697: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.697: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.697: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.697: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.697: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.697: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.697: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.697: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.697: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.697: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.698: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.698: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.698: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.698: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.698: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.698: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.698: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.698: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.698: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.698: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.698: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.698: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.698: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.698: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.698: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.698: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.699: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.699: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.699: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.699: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.699: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.699: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.699: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.699: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.699: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.699: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.699: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.699: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.699: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.699: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.700: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.700: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.700: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.700: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.700: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.700: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.700: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.700: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.700: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.700: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.701: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.701: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.701: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.701: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.701: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.701: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.701: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.701: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.701: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.701: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.701: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.701: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.701: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.701: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.701: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.702: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.702: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.702: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.702: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.702: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.702: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.702: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.702: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.702: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.702: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.702: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.702: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.702: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.702: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.702: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.702: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.703: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.703: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.703: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.703: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.703: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.703: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.703: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.703: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.703: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.703: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.703: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.704: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.704: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.704: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.704: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.704: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.704: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.704: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.704: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.704: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.704: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.704: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.704: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.704: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.704: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.705: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.705: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.705: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.705: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.705: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.705: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.705: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.705: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.705: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.705: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.705: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.705: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.705: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.705: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.706: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.706: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.706: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.706: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.706: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.706: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.706: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.706: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.706: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.706: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.707: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.707: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.707: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.707: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.707: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.707: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.707: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.707: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.707: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.707: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.707: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.707: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.707: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.707: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.708: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.708: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.708: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.708: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.708: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.708: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.708: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.708: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.708: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.708: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.709: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.709: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.709: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.709: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.709: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.709: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.709: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.709: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.709: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.709: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.709: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.709: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.709: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.709: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.710: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.710: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.710: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.710: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.710: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.710: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.710: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.710: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.710: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.710: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.711: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.711: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.711: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.711: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.711: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.711: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.711: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.711: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.711: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.711: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.711: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.711: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.711: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.711: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.712: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.712: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.712: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.712: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.712: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.712: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.712: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.712: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.712: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.712: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.713: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.713: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.713: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.713: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.713: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.713: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.713: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.713: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.713: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.713: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.713: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.713: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.713: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.713: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.714: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.714: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.714: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.714: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.714: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.714: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.714: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.714: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.714: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.714: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.715: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.715: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.715: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.715: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.715: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.715: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.715: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.715: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.715: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.715: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.715: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.715: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.715: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.715: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.716: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.716: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.716: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.716: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.716: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.716: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.716: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.716: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.716: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.716: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.717: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.717: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.717: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.717: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.717: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.717: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.717: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.717: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.717: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.717: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.717: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.717: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.717: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.717: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.718: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.718: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.718: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.718: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.718: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.718: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.718: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.718: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.718: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.718: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.718: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.718: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.718: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.718: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.718: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.718: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.719: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.719: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.719: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.719: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.719: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.719: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.719: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.719: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.719: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.719: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.720: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.720: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.720: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.720: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.720: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.720: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.720: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.720: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.720: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.720: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.720: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.720: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.720: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.720: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.721: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.721: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.721: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.721: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.721: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.721: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.721: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.721: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.721: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.721: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.722: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.722: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.722: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.722: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.722: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.722: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.722: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.722: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.722: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.722: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.722: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.722: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.722: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.722: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.722: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.722: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.723: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.723: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.723: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.723: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.723: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.723: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.723: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.723: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.723: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.723: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.723: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.723: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.723: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.723: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.724: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.724: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.724: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.724: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.724: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.724: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.724: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.724: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.724: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.724: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.725: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.725: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.725: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.725: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.725: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.725: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.725: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.725: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.725: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.725: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.725: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.725: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.725: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.725: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.726: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.726: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.726: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.726: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.726: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.726: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.726: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.726: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.726: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.726: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.727: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.727: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.727: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.727: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.727: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.727: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.727: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.727: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.727: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.727: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.727: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.727: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.727: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.727: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.727: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.727: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.728: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.728: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.728: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.728: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.728: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.728: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.728: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.728: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.728: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.728: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.728: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.728: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.728: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.728: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.728: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.728: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.729: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.729: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.729: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.729: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.729: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.729: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.729: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.729: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.729: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.729: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.729: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.729: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.729: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.729: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.730: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.730: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.730: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.730: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.730: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.730: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.730: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.730: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.730: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.730: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.730: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.730: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.730: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.730: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.730: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.730: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.731: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.731: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.731: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.731: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.731: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.731: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.731: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.731: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.731: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.731: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.732: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.732: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.732: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.732: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.732: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.732: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.732: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.732: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.732: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.732: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.732: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.732: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.732: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.732: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.733: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.733: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.733: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.733: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.733: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.733: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.733: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.733: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.733: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.733: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.734: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.734: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.734: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.734: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.734: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.734: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.734: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.734: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.734: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.734: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.735: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.735: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.735: variance_after = 1526
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.735: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.735: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.735: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.735: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.735: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.735: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.736: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.736: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.736: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.736: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.736: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.736: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.736: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.736: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.736: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.736: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.736: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.736: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.736: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.736: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.736: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.737: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.737: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.737: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.737: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.737: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.737: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.737: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.737: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.737: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.737: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.737: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.737: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.737: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.737: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.738: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.738: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.738: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.738: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.738: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.738: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.738: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.738: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.738: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.738: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.739: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.739: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.739: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.739: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.739: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.739: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.739: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.739: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.739: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.739: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.739: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.739: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.739: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.739: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.740: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.740: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.740: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.740: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.740: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.740: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.740: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.740: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.740: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.740: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.741: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.741: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.741: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.741: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.741: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.741: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.741: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.741: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.741: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.741: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.741: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.741: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.741: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.741: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.742: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.742: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.742: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.742: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.742: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.742: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.742: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.742: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.742: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.742: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.743: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.743: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.743: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.743: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.743: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.743: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.743: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.743: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.743: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.743: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.743: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.743: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.743: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.743: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.743: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.743: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.744: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.744: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.744: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.744: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.744: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.744: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.744: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.744: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.744: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.744: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.744: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.744: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.744: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.744: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.744: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.745: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.745: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.745: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.745: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.745: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.745: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.745: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.745: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.745: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.745: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.745: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.745: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.745: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.745: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.745: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.746: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.746: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.746: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.746: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.746: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.746: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.746: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.746: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.746: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.746: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.747: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.747: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.747: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.747: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.747: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.747: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.747: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.747: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.747: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.747: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.747: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.747: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.747: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.747: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.747: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.747: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.748: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.748: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.748: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.748: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.748: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.748: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.748: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.748: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.748: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.748: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.748: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.748: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.748: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.748: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.748: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.748: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.749: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.749: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.749: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.749: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.749: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.749: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.749: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.749: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.749: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.749: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.749: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.749: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.749: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.749: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.749: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.749: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.750: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.750: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.750: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.750: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.750: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.750: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.750: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.750: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.751: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.751: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.751: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.751: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.751: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.751: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.751: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.751: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.751: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.751: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.751: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.751: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.751: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.751: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.751: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.751: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.752: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.752: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.752: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.752: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.752: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.752: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.752: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.752: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.752: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.752: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.752: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.752: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.752: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.752: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.753: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.753: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.753: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.753: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.753: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.753: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.753: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.753: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.753: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.753: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.754: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.754: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.754: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.754: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.754: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.754: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.754: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.754: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.754: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.754: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.754: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.754: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.754: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.754: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.754: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.755: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.755: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.755: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.755: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.755: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.755: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.755: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.755: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.755: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.756: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.756: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.756: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.756: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.756: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.756: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.756: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.756: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.756: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.756: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.756: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.756: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.756: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.756: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.757: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.757: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.757: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.757: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.757: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.757: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.757: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.757: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.757: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.757: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.757: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.757: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.757: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.757: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.757: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.757: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.758: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.758: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.758: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.758: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.758: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.758: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.758: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.758: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.758: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.758: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.759: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.759: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.759: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.759: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.759: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.759: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.759: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.759: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.759: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.759: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.759: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.759: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.759: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.759: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.760: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.760: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.760: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.760: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.760: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.760: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.760: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.760: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.760: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.760: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.760: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.760: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.760: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.760: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.760: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.760: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.761: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.761: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.761: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.761: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.761: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.761: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.761: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.761: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.761: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.761: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.761: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.762: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.762: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.762: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.762: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.762: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.762: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.762: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.762: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.762: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.762: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.762: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.762: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.762: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.762: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.762: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.763: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.763: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.763: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.763: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.763: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.763: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.763: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.763: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.763: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.763: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.763: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.763: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.763: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.763: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.764: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.764: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.764: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.764: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.764: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.764: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.764: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.764: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.764: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.764: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.764: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.764: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.764: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.764: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.764: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.764: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.765: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.765: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.765: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.765: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.765: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.765: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.765: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.765: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.765: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.765: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.766: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.766: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.766: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.766: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.766: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.766: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.766: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.766: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.766: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.766: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.766: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.766: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.766: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.766: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.766: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.766: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.767: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.767: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.767: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.767: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.767: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.767: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.767: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.767: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.767: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.767: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.767: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.767: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.767: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.767: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.767: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.767: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.768: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.768: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.768: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.768: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.768: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.768: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.768: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.768: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.768: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.768: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.768: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.768: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.768: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.768: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.769: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.769: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.769: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.769: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.769: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.769: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.769: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.769: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.769: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.769: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.770: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.770: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.770: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.770: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.770: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.770: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.770: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.770: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.770: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.770: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.770: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.770: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.770: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.770: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.771: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.771: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.771: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.771: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.771: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.771: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.771: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.771: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.771: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.771: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.772: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.772: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.772: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.772: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.772: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.772: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.772: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.772: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.772: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.772: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.772: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.772: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.772: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.772: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.773: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.773: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.773: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.773: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.773: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.773: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.773: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.773: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.773: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.773: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.774: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.774: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.774: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.774: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.774: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.774: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.774: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.774: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.774: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.774: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.774: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.774: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.774: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.774: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.775: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.775: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.775: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.775: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.775: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.775: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.775: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.775: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.775: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.775: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.776: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.776: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.776: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.776: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.776: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.776: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.776: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.776: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.776: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.776: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.776: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.776: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.776: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.776: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.776: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.776: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.777: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.777: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.777: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.777: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.777: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.777: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.777: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.777: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.777: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.777: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.777: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.777: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.777: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.777: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.778: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.778: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.778: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.778: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.778: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.778: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.778: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.778: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.778: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.778: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.778: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.778: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.778: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.778: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.778: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.778: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.779: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.779: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.779: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.779: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.779: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.779: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.779: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.779: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.779: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.779: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.780: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.780: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.780: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.780: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.780: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.780: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.780: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.780: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.780: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.780: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.780: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.780: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.780: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.780: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.780: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.780: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.781: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.781: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.781: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.781: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.781: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.781: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.781: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.781: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.781: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.781: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.781: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.782: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.782: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.782: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.782: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.782: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.782: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.782: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.782: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.782: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.782: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.782: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.782: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.782: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.783: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.783: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.783: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.783: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.783: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.783: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.783: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.783: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.783: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.783: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.783: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.783: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.783: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.783: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.784: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.784: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.784: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.784: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.784: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.784: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.784: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.784: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.784: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.784: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.785: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.785: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.785: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.785: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.785: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.785: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.785: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.785: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.785: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.785: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.785: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.785: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.785: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.785: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.785: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.785: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.786: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.786: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.786: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.786: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.786: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.786: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.786: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.786: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.786: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.786: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.786: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.786: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.786: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.786: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.787: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.787: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.787: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.787: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.787: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.787: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.787: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.787: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.787: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.787: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.788: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.788: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.788: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.788: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.788: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.788: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.788: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.788: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.788: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.788: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.788: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.788: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.788: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.788: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.789: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.789: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.789: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.789: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.789: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.789: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.789: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.789: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.789: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.789: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.790: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.790: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.790: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.790: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.790: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.790: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.790: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.790: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.790: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.790: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.790: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.790: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.790: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.790: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.790: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.790: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.791: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.791: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.791: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.791: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.791: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.791: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.791: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.791: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.791: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.791: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.791: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.791: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.791: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.791: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.792: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.792: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.792: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.792: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.792: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.792: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.792: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.792: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.792: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.792: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.793: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.793: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.793: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.793: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.793: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.793: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.793: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.793: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.793: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.793: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.793: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.793: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.793: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.793: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.793: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.793: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.794: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.794: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.794: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.794: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.794: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.794: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.794: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.794: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.794: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.794: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.794: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.794: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.794: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.794: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.794: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.794: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.795: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.795: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.795: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.795: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.795: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.795: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.795: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.795: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.795: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.795: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.795: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.795: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.795: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.795: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.796: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.796: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.796: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.796: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.796: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.796: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.796: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.796: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.796: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.796: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.796: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.796: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.796: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.796: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.796: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.796: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.797: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.797: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.797: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.797: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.797: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.797: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.797: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.797: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.797: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.797: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.798: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.798: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.798: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.798: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.798: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.798: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.798: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.798: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.798: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.798: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.798: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.798: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.798: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.798: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.798: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.798: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.799: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.799: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.799: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.799: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.799: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.799: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.799: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.799: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.800: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.800: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.800: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.800: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.800: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.800: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.800: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.800: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.800: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.800: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.800: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.800: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.800: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.800: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.801: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.801: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.801: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.801: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.801: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.801: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.801: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.801: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.801: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.801: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.802: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.802: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.802: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.802: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.802: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.802: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.802: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.802: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.802: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.802: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.802: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.802: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.802: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.802: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.802: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.802: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.803: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.803: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.803: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.803: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.803: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.803: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.803: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.803: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.803: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.803: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.803: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.803: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.803: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.803: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.804: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.804: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.804: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.804: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.804: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.804: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.804: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.804: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.804: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.804: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.805: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.805: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.805: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.805: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.805: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.805: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.805: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.805: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.805: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.805: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.805: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.805: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.805: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.805: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.805: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.805: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.806: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.806: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.806: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.806: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.806: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.806: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.806: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.806: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.806: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.806: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.806: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.806: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.806: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.806: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.807: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.807: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.807: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.807: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.807: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.807: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.807: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.807: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.807: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.807: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.808: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.808: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.808: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.808: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.808: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.808: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.808: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.808: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.808: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.808: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.808: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.808: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.808: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.808: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.808: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.808: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.809: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.809: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.809: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.809: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.809: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.809: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.809: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.809: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.809: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.809: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.809: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.809: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.809: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.809: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.810: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.810: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.810: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.810: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.810: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.810: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.810: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.810: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.810: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.810: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.810: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.810: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.810: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.810: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.810: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.810: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.811: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.811: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.811: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.811: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.811: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.811: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.811: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.811: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.811: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.811: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.812: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.812: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.812: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.812: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.812: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.812: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.812: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.812: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.812: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.812: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.812: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.812: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.812: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.812: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.812: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.813: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.813: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.813: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.813: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.813: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.813: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.813: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.813: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.813: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.813: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.813: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.813: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.813: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.813: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.813: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.814: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.814: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.814: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.814: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.814: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.814: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.814: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.814: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.814: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.814: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.815: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.815: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.815: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.815: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.815: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.815: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.815: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.815: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.815: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.815: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.815: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.815: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.815: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.815: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.816: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.816: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.816: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.816: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.816: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.816: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.816: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.816: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.816: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.816: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.816: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.816: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.816: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.816: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.816: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.816: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.817: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.817: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.817: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.817: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.817: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.817: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.817: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.817: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.817: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.817: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.817: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.817: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.818: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.818: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.818: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.818: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.818: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.818: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.818: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.818: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.818: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.818: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.818: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.818: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.818: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.818: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.819: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.819: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.819: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.819: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.819: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.819: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.819: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.819: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.819: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.819: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.819: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.819: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.819: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.819: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.819: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.819: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.820: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.820: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.820: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.820: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.820: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.820: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.820: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.820: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.820: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.820: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.820: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.820: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.820: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.820: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.821: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.821: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.821: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.821: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.821: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.821: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.821: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.821: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.821: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.821: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.821: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.822: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.822: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.822: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.822: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.822: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.822: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.822: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.822: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.822: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.822: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.822: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.822: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.822: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.822: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.822: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.823: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.823: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.823: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.823: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.823: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.823: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.823: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.823: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.823: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.823: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.823: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.823: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.823: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.823: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.824: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.824: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.824: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.824: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.824: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.824: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.824: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.825: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.825: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.825: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.825: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.825: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.825: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.825: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.825: variance_after = 1435
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.825: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.825: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.825: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.826: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.826: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.826: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.826: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.826: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.826: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.826: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.826: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.827: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.827: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.827: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.827: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.827: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.827: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.827: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.827: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.827: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.827: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.827: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.828: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.828: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.828: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.828: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.828: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.828: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.828: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.828: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.828: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.828: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.828: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.828: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.828: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.828: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.829: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.829: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.829: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.829: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.829: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.829: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.829: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.829: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.829: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.829: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.829: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.829: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.829: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.829: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.829: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.830: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.830: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.830: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.830: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.830: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.830: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.830: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.830: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.830: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.830: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.831: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.831: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.831: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.831: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.831: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.831: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.831: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.831: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.831: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.831: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.831: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.831: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.831: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.831: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.832: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.832: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.832: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.832: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.832: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.832: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.832: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.832: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.832: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.832: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.832: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.832: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.832: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.832: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.832: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.832: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.833: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.833: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.833: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.833: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.833: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.833: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.833: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.833: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.833: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.833: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.834: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.834: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.834: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.834: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.834: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.834: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.834: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.834: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.834: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.834: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.834: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.834: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.834: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.834: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.835: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.835: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.835: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.835: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.835: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.835: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.835: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.835: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.835: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.835: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.836: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.836: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.836: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.836: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.836: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.836: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.836: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.836: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.836: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.836: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.836: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.836: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.836: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.836: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.836: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.836: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.837: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.837: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.837: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.837: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.837: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.837: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.837: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.837: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.837: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.837: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.837: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.837: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.837: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.837: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.838: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.838: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.838: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.838: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.838: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.838: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.838: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.838: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.838: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.838: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.839: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.839: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.839: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.839: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.839: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.839: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.839: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.839: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.839: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.839: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.839: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.839: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.839: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.839: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.839: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.839: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.840: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.840: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.840: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.840: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.840: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.840: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.840: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.840: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.840: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.840: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.840: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.840: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.840: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.840: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.841: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.841: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.841: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.841: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.841: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.841: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.841: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.841: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.841: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.841: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.841: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.841: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.841: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.841: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.841: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.842: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.842: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.842: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.842: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.842: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.842: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.842: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.842: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.842: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.842: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.842: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.843: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.843: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.843: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.843: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.843: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.843: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.843: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.843: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.843: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.843: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.843: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.843: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.843: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.843: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.843: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.843: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.844: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.844: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.844: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.844: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.844: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.844: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.844: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.844: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.844: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.844: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.844: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.844: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.844: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.844: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.845: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.845: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.845: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.845: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.845: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.845: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.845: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.845: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.845: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.845: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.845: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.845: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.845: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.845: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.845: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.845: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.846: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.846: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.846: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.846: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.846: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.846: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.846: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.846: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.846: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.846: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.847: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.847: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.847: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.847: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.847: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.847: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.847: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.847: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.847: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.847: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.847: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.847: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.847: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.847: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.848: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.848: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.848: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.848: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.848: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.848: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.848: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.848: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.848: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.848: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.848: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.848: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.848: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.848: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.848: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.848: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.849: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.849: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.849: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.849: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.849: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.849: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.849: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.849: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.849: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.849: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.850: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.850: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.850: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.850: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.850: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.850: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.850: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.850: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.850: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.850: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.850: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.850: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.850: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.850: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.851: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.851: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.851: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.851: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.851: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.851: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.851: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.851: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.851: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.851: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.851: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.852: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.852: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.852: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.852: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.852: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.852: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.852: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.852: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.852: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.852: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.852: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.852: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.852: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.852: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.852: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.852: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.852: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.852: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.853: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.853: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.853: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.853: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.853: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.853: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.853: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.853: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.853: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.853: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.853: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.853: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.853: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.854: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.854: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.854: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.854: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.854: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.854: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.854: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.854: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.854: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.854: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.854: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.854: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.854: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.854: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.855: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.855: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.855: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.855: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.855: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.855: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.855: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.855: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.855: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.855: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.856: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.856: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.856: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.856: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.856: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.856: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.856: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.856: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.856: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.856: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.856: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.856: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.856: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.856: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.856: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.856: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.857: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.857: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.857: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.857: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.857: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.857: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.857: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.857: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.857: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.857: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.857: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.857: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.857: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.857: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.858: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.858: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.858: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.858: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.858: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.858: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.858: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.858: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.858: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.858: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.859: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.859: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.859: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.859: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.859: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.859: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.859: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.859: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.859: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.859: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.859: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.859: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.859: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.859: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.859: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.859: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.860: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.860: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.860: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.860: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.860: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.860: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.860: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.860: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.860: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.860: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.860: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.860: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.860: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.860: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.861: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.861: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.861: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.861: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.861: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.861: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.861: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.861: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.861: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.861: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.861: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.861: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.861: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.861: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.861: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.861: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.862: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.862: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.862: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.862: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.862: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.862: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.862: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.862: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.862: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.862: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.863: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.863: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.863: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.863: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.863: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.863: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.863: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.863: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.863: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.863: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.863: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.863: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.863: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.863: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.863: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.863: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.864: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.864: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.864: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.864: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.864: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.864: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.864: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.864: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.864: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.864: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.864: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.864: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.864: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.864: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.864: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.864: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.865: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.865: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.865: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.865: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.865: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.865: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.865: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.865: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.865: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.865: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.865: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.865: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.865: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.865: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.866: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.866: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.866: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.866: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.866: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.866: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.866: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.866: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.866: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.866: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.866: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.866: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.866: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.866: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.866: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.866: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.867: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.867: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.867: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.867: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.867: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.867: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.867: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.867: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.867: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.867: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.868: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.868: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.868: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.868: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.868: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.868: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.868: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.868: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.868: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.868: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.868: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.868: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.868: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.868: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.868: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.868: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.869: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.869: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.869: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.869: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.869: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.869: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.869: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.869: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.869: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.869: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.869: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.869: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.869: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.869: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.870: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.870: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.870: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.870: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.870: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.870: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.870: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.870: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.870: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.870: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.871: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.871: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.871: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.871: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.871: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.871: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.871: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.871: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.871: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.871: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.871: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.871: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.871: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.871: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.872: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.872: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.872: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.872: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.872: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.872: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.872: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.872: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.872: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.872: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.873: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.873: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.873: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.873: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.873: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.873: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.873: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.873: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.873: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.873: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.873: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.873: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.873: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.873: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.874: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.874: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.874: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.874: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.874: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.874: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.874: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.874: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.874: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.874: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.875: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.875: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.875: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.875: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.875: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.875: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.875: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.875: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.875: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.875: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.875: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.875: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.875: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.875: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.876: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.876: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.876: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.876: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.876: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.876: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.876: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.876: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.876: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.876: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.877: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.877: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.877: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.877: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.877: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.877: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.877: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.877: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.877: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.877: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.877: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.877: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.877: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.877: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.877: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.877: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.878: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.878: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.878: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.878: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.878: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.878: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.878: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.878: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.878: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.878: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.878: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.878: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.878: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.878: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.879: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.879: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.879: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.879: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.879: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.879: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.879: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.879: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.879: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.879: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.880: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.880: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.880: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.880: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.880: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.880: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.880: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.880: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.880: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.880: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.880: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.880: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.880: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.880: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.881: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.881: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.881: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.881: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.881: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.881: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.881: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.881: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.881: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.881: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.882: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.882: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.882: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.882: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.882: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.882: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.882: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.882: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.882: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.882: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.882: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.882: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.882: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.882: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.882: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.882: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.883: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.883: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.883: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.883: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.883: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.883: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.883: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.883: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.883: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.883: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.883: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.883: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.883: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.883: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.883: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.884: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.884: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.884: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.884: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.884: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.884: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.884: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.884: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.884: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.884: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.884: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.884: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.884: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.884: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.884: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.885: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.885: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.885: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.885: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.885: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.885: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.885: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.885: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.885: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.885: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.886: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.886: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.886: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.886: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.886: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.886: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.886: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.886: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.886: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.886: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.886: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.886: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.886: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.886: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.886: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.886: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.887: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.887: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.887: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.887: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.887: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.887: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.887: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.887: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.887: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.887: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.887: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.887: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.887: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.887: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.888: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.888: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.888: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.888: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.888: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.888: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.888: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.888: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.888: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.888: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.888: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.889: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.889: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.889: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.889: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.889: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.889: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.889: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.889: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.889: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.889: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.889: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.889: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.889: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.890: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.890: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.890: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.890: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.890: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.890: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.890: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.890: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.890: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.890: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.891: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.891: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.891: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.891: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.891: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.891: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.891: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.891: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.891: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.891: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.891: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.891: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.891: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.891: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.891: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.892: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.892: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.892: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.892: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.892: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.892: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.892: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.892: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.892: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.892: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.892: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.892: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.892: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.892: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.892: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.893: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.893: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.893: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.893: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.893: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.893: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.893: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.893: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.893: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.894: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.894: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.894: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.894: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.894: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.894: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.894: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.894: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.894: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.894: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.895: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.895: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.895: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.895: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.895: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.895: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.895: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.895: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.895: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.895: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.895: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.895: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.895: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.896: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.896: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.896: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.896: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.896: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.896: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.896: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.896: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.896: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.896: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.897: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.897: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.897: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.897: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.897: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.897: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.897: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.897: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.898: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.898: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.898: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.898: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.898: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.898: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.898: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.898: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.898: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.898: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.898: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.898: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.898: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.898: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.898: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.898: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.899: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.899: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.899: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.899: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.899: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.899: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.899: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.899: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.899: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.899: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.899: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.899: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.899: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.899: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.900: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.900: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.900: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.900: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.900: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.900: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.900: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.900: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.900: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.900: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.901: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.901: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.901: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.901: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.901: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.901: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.901: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.901: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.901: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.901: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.901: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.901: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.901: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.901: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.902: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.902: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.902: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.902: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.902: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.902: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.902: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.902: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.903: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.903: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.903: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.903: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.903: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.903: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.903: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.903: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.903: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.903: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.904: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.904: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.904: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.904: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.904: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.904: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.904: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.904: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.904: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.904: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.904: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.904: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.904: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.904: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.905: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.905: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.905: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.905: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.905: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.905: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.905: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.905: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.905: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.905: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.906: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.906: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.906: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.906: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.906: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.906: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.906: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.906: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.906: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.906: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.906: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.906: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.906: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.906: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.907: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.907: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.907: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.907: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.907: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.907: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.907: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.907: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.907: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.907: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.908: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.908: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.908: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.908: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.908: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.908: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.908: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.908: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.908: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.908: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.908: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.908: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.908: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.908: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.909: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.909: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.909: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.909: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.909: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.909: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.909: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.909: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.909: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.909: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.910: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.910: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.910: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.910: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.910: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.910: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.910: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.910: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.910: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.910: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.910: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.910: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.910: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.910: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.911: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.911: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.911: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.911: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.911: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.911: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.911: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.911: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.911: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.911: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.911: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.911: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.911: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.911: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.911: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.911: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.912: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.912: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.912: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.912: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.912: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.912: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.912: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.912: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.912: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.912: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.912: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.912: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.912: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.912: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.912: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.912: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.913: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.913: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.913: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.913: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.913: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.913: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.913: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.913: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.913: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.913: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.913: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.913: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.913: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.913: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.913: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.913: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.914: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.914: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.914: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.914: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.914: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.914: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.914: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.914: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.914: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.914: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.915: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.915: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.915: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.915: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.915: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.915: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.915: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.915: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.915: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.915: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.916: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.916: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.916: variance_after = 1425
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.916: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.916: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.916: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.916: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.916: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.917: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.917: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.917: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.917: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.917: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.917: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.917: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.917: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.917: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.917: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.917: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.917: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.917: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.917: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.918: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.918: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.918: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.918: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.918: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.918: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.918: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.918: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.918: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.918: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.919: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.919: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.919: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.919: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.919: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.919: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.919: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.919: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.919: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.919: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.919: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.919: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.919: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.919: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.919: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.920: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.920: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.920: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.920: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.920: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.920: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.920: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.920: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.920: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.920: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.920: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.920: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.920: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.920: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.920: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.921: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.921: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.921: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.921: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.921: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.921: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.921: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.921: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.921: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.921: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.922: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.922: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.922: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.922: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.922: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.922: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.922: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.922: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.922: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.922: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.922: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.922: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.922: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.922: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.923: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.923: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.923: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.923: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.923: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.923: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.923: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.923: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.923: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.923: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.924: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.924: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.924: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.924: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.924: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.924: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.924: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.924: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.924: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.924: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.924: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.924: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.924: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.924: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.924: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.924: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.925: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.925: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.925: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.925: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.925: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.925: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.925: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.925: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.925: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.926: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.926: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.926: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.926: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.926: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.926: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.926: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.926: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.926: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.926: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.926: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.926: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.926: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.926: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.926: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.927: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.927: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.927: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.927: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.927: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.927: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.927: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.927: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.927: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.927: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.927: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.927: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.927: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.927: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.928: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.928: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.928: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.928: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.928: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.928: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.928: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.928: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.928: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.928: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.929: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.929: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.929: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.929: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.929: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.929: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.929: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.929: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.929: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.929: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.929: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.929: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.929: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.929: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.930: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.930: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.930: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.930: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.930: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.930: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.930: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.930: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.930: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.930: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.930: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.930: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.930: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.930: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.930: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.930: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.931: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.931: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.931: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.931: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.931: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.931: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.931: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.931: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.931: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.932: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.932: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.932: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.932: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.932: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.932: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.932: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.932: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.932: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.932: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.932: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.932: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.932: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.932: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.932: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.933: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.933: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.933: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.933: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.933: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.933: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.933: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.933: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.933: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.933: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.933: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.933: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.933: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.933: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.933: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.933: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.934: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.934: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.934: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.934: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.934: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.934: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.934: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.934: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.934: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.934: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.935: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.935: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.935: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.935: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.935: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.935: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.935: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.935: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.935: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.935: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.935: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.935: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.935: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.935: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.935: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.935: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.936: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.936: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.936: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.936: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.936: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.936: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.936: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.936: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.936: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.936: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.936: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.936: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.936: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.936: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.937: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.937: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.937: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.937: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.937: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.937: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.937: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.937: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.937: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.937: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.938: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.938: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.938: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.938: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.938: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.938: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.938: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.938: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.938: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.938: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.938: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.938: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.938: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.938: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.939: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.939: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.939: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.939: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.939: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.939: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.939: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.939: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.939: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.939: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.940: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.940: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.940: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.940: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.940: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.940: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.940: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.940: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.940: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.940: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.940: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.940: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.940: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.940: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.940: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.940: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.941: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.941: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.941: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.941: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.941: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.941: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.941: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.941: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.941: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.942: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.942: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.942: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.942: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.942: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.942: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.942: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.942: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.942: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.942: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.942: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.942: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.942: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.943: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.943: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.943: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.943: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.943: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.943: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.943: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.943: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.943: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.943: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.943: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.943: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.943: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.943: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.943: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.943: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.944: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.944: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.944: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.944: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.944: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.944: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.944: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.944: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.945: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.945: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.945: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.945: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.945: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.945: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.945: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.945: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.945: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.945: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.946: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.946: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.946: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.946: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.946: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.946: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.946: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.946: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.946: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.946: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.946: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.946: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.946: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.946: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.946: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.946: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.947: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.947: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.947: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.947: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.947: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.947: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.947: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.947: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.947: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.947: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.947: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.947: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.947: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.947: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.948: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.948: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.948: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.948: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.948: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.948: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.948: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.948: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.948: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.948: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.949: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.949: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.949: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.949: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.949: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.949: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.949: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.949: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.949: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.949: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.949: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.949: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.949: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.949: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.950: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.950: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.950: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.950: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.950: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.950: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.950: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.950: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.950: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.950: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.950: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.950: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.950: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.950: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.950: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.950: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.951: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.951: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.951: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.951: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.951: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.951: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.951: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.951: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.951: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.951: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.952: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.952: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.952: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.952: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.952: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.952: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.952: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.952: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.952: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.952: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.952: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.952: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.952: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.952: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.952: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.953: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.953: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.953: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.953: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.953: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.953: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.953: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.953: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.953: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.953: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.953: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.953: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.953: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.953: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.953: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.954: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.954: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.954: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.954: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.954: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.954: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.954: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.954: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.954: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.954: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.955: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.955: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.955: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.955: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.955: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.955: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.955: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.955: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.955: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.955: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.955: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.955: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.955: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.955: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.956: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.956: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.956: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.956: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.956: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.956: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.956: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.956: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.956: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.956: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.957: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.957: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.957: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.957: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.957: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.957: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.957: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.957: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.957: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.957: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.957: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.957: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.957: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.958: [vfs7552] CAPTURE_NUM_STATES entering state 2
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.958: [vfs7552] REQUEST CHUNK entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.958: Sending vfs7552_read_image_chunk
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.958: [vfs7552] REQUEST CHUNK completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.958: [vfs7552] CAPTURE_NUM_STATES entering state 3
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.958: [vfs7552] CAPTURE_NUM_STATES entering state 4
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.958: Cleaning image
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.959: variance_after = 1532
173s 
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.959: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.959: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.959: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.959: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.959: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.959: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.959: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.959: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.959: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.959: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.959: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.959: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.959: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.960: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.960: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.960: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.960: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.960: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.960: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.960: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.960: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.960: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.960: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.960: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.960: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.960: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.960: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.961: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.961: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.961: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.961: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.961: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.961: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.961: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.961: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.961: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.961: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.962: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.962: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.962: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.962: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.962: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.962: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.962: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.962: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.962: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.962: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.962: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.962: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.962: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.962: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.962: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.962: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.963: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.963: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.963: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.963: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.963: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.963: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.963: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.963: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.963: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.963: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.963: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.963: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.963: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.963: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.964: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.964: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.964: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.964: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.964: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.964: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.964: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.964: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.964: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.964: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.965: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.965: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.965: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.965: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.965: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.965: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.965: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.965: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.965: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.965: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.965: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.965: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.965: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.965: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.965: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.965: Receiving 64 bytes
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.966: Got 6 bytes out of 64
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.966: [vfs7552] QUERY DATA READY completed successfully
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.966: [vfs7552] CAPTURE_NUM_STATES entering state 1
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.966: [vfs7552] CAPTURE_NUM_STATES entering state 0
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.966: [vfs7552] QUERY DATA READY entering state 0
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.966: Sending vfs7552_is_image_ready
173s (process:2479): libfprint-SSM-DEBUG: 05:03:04.966: [vfs7552] QUERY DATA READY entering state 1
173s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.966: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.966: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.966: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.966: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.966: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.966: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.966: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.967: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.967: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.967: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.967: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.967: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.967: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.967: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.967: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.967: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.967: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.967: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.967: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.967: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.967: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.967: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.967: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.968: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.968: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.968: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.968: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.968: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.968: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.968: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.968: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.968: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.968: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.968: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.968: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.968: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.968: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.968: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.968: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.969: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.969: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.969: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.969: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.969: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.969: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.969: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.969: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.969: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.969: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.969: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.969: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.969: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.969: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.969: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.969: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.970: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.970: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.970: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.970: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.970: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.970: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.970: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.970: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.970: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.970: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.970: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.970: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.970: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.970: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.970: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.970: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.971: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.971: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.971: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.971: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.971: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.971: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.971: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.971: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.971: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.971: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.972: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.972: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.972: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.972: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.972: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.972: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.972: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.972: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.972: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.972: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.972: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.972: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.972: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.972: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.973: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.973: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.973: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.973: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.973: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.973: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.973: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.973: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.973: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.973: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.973: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.973: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.973: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.973: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.973: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.973: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.974: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.974: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.974: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.974: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.974: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.974: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.974: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.974: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.974: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.974: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.975: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.975: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.975: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.975: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.975: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.975: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.975: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.975: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.975: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.975: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.975: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.975: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.975: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.975: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.976: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.976: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.976: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.976: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.976: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.976: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.976: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.976: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.976: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.976: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.976: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.977: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.977: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.977: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.977: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.977: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.977: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.977: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.977: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.977: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.977: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.977: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.977: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.977: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.977: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.977: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.978: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.978: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.978: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.978: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.978: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.978: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.978: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.978: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.978: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.978: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.978: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.978: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.978: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.978: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.978: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.979: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.979: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.979: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.979: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.979: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.979: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.979: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.979: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.979: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.979: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.980: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.980: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.980: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.980: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.980: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.980: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.980: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.980: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.980: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.980: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.980: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.980: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.980: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.980: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.980: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.981: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.981: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.981: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.981: [vfs7552] CAPTURE_NUM_STATES entering state 2
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.981: [vfs7552] REQUEST CHUNK entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.981: Sending vfs7552_read_image_chunk
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.981: [vfs7552] REQUEST CHUNK completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.981: [vfs7552] CAPTURE_NUM_STATES entering state 3
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.981: [vfs7552] CAPTURE_NUM_STATES entering state 2
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.981: [vfs7552] REQUEST CHUNK entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.981: Sending vfs7552_read_image_chunk
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.982: [vfs7552] REQUEST CHUNK completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.982: [vfs7552] CAPTURE_NUM_STATES entering state 3
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.982: [vfs7552] CAPTURE_NUM_STATES entering state 2
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.982: [vfs7552] REQUEST CHUNK entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.982: Sending vfs7552_read_image_chunk
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.982: [vfs7552] REQUEST CHUNK completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.982: [vfs7552] CAPTURE_NUM_STATES entering state 3
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.983: [vfs7552] CAPTURE_NUM_STATES entering state 4
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.983: Cleaning image
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.983: variance_after = 1691
174s 
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.983: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.983: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.983: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.983: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.983: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.983: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.983: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.983: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.983: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.983: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.984: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.984: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.984: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.984: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.984: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.984: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.984: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.984: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.984: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.984: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.984: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.985: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.985: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.985: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.985: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.985: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.985: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.985: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.985: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.985: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.985: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.985: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.985: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.985: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.985: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.986: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.986: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.986: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.986: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.986: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.986: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.986: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.986: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.986: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.986: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.987: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.987: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.987: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.987: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.987: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.987: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.987: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.987: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.987: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.987: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.987: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.987: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.987: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.987: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.988: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.988: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.988: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.988: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.988: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.988: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.988: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.988: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.988: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.988: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.989: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.989: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.989: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.989: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.989: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.989: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.989: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.989: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.989: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.989: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.989: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.989: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.989: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.989: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.990: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.990: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.990: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.990: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.990: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.990: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.990: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.990: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.990: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.990: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.991: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.991: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.991: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.991: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.991: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.991: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.991: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.991: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.991: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.991: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.991: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.991: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.991: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.991: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.992: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.992: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.992: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.992: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.992: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.992: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.992: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.992: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.992: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.992: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.993: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.993: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.993: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.993: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.993: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.993: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.993: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.993: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.993: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.993: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.993: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.993: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.993: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.993: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.993: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.993: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.994: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.994: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.994: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.994: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.994: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.994: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.994: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.994: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.994: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.994: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.994: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.994: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.994: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.994: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.995: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.995: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.995: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.995: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.995: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.995: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.995: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.995: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.995: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.995: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.996: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.996: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.996: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.996: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.996: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.996: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.996: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.996: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.996: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.996: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.996: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.996: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.996: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.996: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.996: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.996: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.997: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.997: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.997: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.997: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.997: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.997: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.997: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.997: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.997: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.997: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.997: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.997: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.997: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.997: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.997: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.997: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.998: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.998: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.998: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.998: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.998: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.998: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.998: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.998: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.998: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.998: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.998: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.998: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.998: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.998: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.998: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.998: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.999: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.999: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.999: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.999: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.999: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.999: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.999: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.999: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.999: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.999: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.999: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.999: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:04.999: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:04.999: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.000: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.000: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.000: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.000: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.000: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.000: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.000: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.000: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.000: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.000: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.000: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.000: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.000: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.000: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.000: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.000: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.001: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.001: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.001: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.001: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.001: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.001: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.001: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.001: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.001: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.001: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.002: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.002: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.002: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.002: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.002: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.002: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.002: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.002: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.002: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.002: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.002: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.002: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.002: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.002: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.003: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.003: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.003: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.003: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.003: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.003: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.003: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.003: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.003: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.003: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.004: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.004: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.004: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.004: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.004: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.004: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.004: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.004: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.004: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.004: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.004: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.004: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.004: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.004: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.005: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.005: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.005: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.005: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.005: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.005: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.005: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.005: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.005: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.005: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.006: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.006: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.006: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.006: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.006: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.006: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.006: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.006: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.006: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.006: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.006: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.006: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.006: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.006: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.006: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.006: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.007: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.007: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.007: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.007: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.007: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.007: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.007: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.007: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.007: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.007: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.007: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.007: [vfs7552] CAPTURE_NUM_STATES entering state 2
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.007: [vfs7552] REQUEST CHUNK entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.007: Sending vfs7552_read_image_chunk
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.008: [vfs7552] REQUEST CHUNK completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.008: [vfs7552] CAPTURE_NUM_STATES entering state 3
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.008: [vfs7552] CAPTURE_NUM_STATES entering state 2
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.008: [vfs7552] REQUEST CHUNK entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.008: Sending vfs7552_read_image_chunk
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.008: [vfs7552] REQUEST CHUNK completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.008: [vfs7552] CAPTURE_NUM_STATES entering state 3
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.009: [vfs7552] CAPTURE_NUM_STATES entering state 2
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.009: [vfs7552] REQUEST CHUNK entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.009: Sending vfs7552_read_image_chunk
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.009: [vfs7552] REQUEST CHUNK completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.009: [vfs7552] CAPTURE_NUM_STATES entering state 3
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.009: [vfs7552] CAPTURE_NUM_STATES entering state 4
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.009: Cleaning image
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.009: variance_after = 1845
174s 
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.009: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.009: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.009: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.010: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.010: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.010: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.010: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.010: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.010: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.010: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.010: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.010: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.010: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.011: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.011: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.011: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.011: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.011: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.011: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.011: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.011: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.011: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.011: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.011: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.011: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.011: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.011: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.012: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.012: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.012: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.012: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.012: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.012: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.012: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.012: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.012: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.012: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.013: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.013: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.013: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.013: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.013: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.013: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.013: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.013: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.013: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.013: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.013: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.013: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.013: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.013: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.014: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.014: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.014: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.014: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.014: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.014: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.014: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.014: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.014: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.014: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.015: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.015: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.015: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.015: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.015: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.015: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.015: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.015: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.015: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.015: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.015: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.015: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.015: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.015: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.016: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.016: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.016: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.016: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.016: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.016: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.016: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.016: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.016: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.016: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.016: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.017: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.017: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.017: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.017: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.017: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.017: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.017: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.017: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.017: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.017: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.017: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.017: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.017: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.017: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.017: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.018: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.018: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.018: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.018: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.018: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.018: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.018: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.018: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.018: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.018: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.018: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.018: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.018: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.018: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.018: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.018: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.019: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.019: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.019: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.019: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.019: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.019: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.019: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.019: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.020: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.020: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.020: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.020: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.020: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.020: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.020: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.020: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.020: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.020: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.020: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.020: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.020: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.020: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.020: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.020: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.021: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.021: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.021: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.021: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.021: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.021: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.021: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.021: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.021: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.021: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.021: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.021: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.021: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.021: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.022: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.022: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.022: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.022: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.022: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.022: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.022: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.022: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.023: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.023: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.023: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.023: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.023: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.023: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.023: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.023: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.023: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.023: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.024: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.024: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.024: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.024: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.024: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.024: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.024: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.024: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.024: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.024: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.024: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.024: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.024: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.024: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.024: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.025: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.025: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.025: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.025: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.025: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.025: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.025: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.025: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.025: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.025: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.025: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.025: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.025: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.025: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.025: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.026: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.026: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.026: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.026: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.026: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.026: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.026: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.026: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.026: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.026: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.027: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.027: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.027: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.027: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.027: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.027: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.027: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.027: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.027: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.027: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.027: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.027: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.027: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.027: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.028: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.028: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.028: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.028: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.028: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.028: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.028: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.028: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.028: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.028: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.028: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.028: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.028: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.028: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.028: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.028: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.029: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.029: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.029: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.029: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.029: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.029: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.029: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.029: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.029: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.029: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.030: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.030: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.030: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.030: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.030: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.030: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.030: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.030: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.030: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.030: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.030: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.030: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.030: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.030: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.031: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.031: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.031: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.031: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.031: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.031: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.031: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.031: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.031: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.031: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.032: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.032: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.032: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.032: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.032: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.032: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.032: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.032: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.032: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.032: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.032: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.032: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.032: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.032: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.033: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.033: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.033: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.033: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.033: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.033: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.033: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.033: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.033: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.033: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.034: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.034: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.034: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.034: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.034: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.034: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.034: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.034: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.034: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.034: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.034: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.034: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.034: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.034: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.035: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.035: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.035: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.035: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.035: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.035: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.035: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.035: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.035: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.035: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.036: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.036: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.036: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.036: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.036: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.036: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.036: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.036: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.036: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.036: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.036: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.036: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.036: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.036: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.037: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.037: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.037: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.037: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.037: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.037: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.037: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.037: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.037: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.037: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.037: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.038: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.038: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.038: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.038: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.038: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.038: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.038: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.038: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.038: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.038: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.038: [vfs7552] CAPTURE_NUM_STATES entering state 2
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.038: [vfs7552] REQUEST CHUNK entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.038: Sending vfs7552_read_image_chunk
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.039: [vfs7552] REQUEST CHUNK completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.039: [vfs7552] CAPTURE_NUM_STATES entering state 3
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.039: [vfs7552] CAPTURE_NUM_STATES entering state 2
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.039: [vfs7552] REQUEST CHUNK entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.039: Sending vfs7552_read_image_chunk
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.039: [vfs7552] REQUEST CHUNK completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.039: [vfs7552] CAPTURE_NUM_STATES entering state 3
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.040: [vfs7552] CAPTURE_NUM_STATES entering state 2
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.040: [vfs7552] REQUEST CHUNK entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.040: Sending vfs7552_read_image_chunk
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.040: [vfs7552] REQUEST CHUNK completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.040: [vfs7552] CAPTURE_NUM_STATES entering state 3
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.040: [vfs7552] CAPTURE_NUM_STATES entering state 4
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.040: Cleaning image
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.040: variance_after = 2342
174s 
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.040: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.040: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.040: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.041: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.041: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.041: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.041: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.041: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.041: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.041: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.041: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.041: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.041: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.042: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.042: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.042: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.042: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.042: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.042: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.042: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.042: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.042: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.042: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.042: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.042: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.042: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.042: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.043: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.043: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.043: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.043: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.043: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.043: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.043: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.043: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.043: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.043: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.043: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.043: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.043: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.043: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.043: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.043: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.044: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.044: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.044: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.044: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.044: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.044: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.044: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.044: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.045: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.045: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.045: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.045: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.045: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.045: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.045: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.045: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.045: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.045: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.045: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.046: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.046: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.046: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.046: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.046: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.046: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.046: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.046: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.046: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.046: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.046: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.046: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.046: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.046: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.046: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.047: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.047: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.047: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.047: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.047: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.047: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.047: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.047: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.047: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.047: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.047: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.047: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.047: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.047: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.048: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.048: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.048: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.048: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.048: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.048: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.048: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.048: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.048: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.048: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.049: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.049: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.049: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.049: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.049: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.049: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.049: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.049: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.049: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.049: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.049: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.049: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.049: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.049: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.050: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.050: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.050: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.050: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.050: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.050: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.050: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.050: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.050: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.050: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.051: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.051: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.051: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.051: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.051: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.051: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.051: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.051: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.051: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.051: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.051: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.051: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.051: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.051: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.052: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.052: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.052: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.052: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.052: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.052: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.052: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.052: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.052: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.052: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.053: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.053: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.053: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.053: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.053: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.053: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.053: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.053: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.053: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.053: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.053: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.053: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.053: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.053: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.054: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.054: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.054: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.054: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.054: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.054: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.054: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.054: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.054: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.054: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.055: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.055: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.055: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.055: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.055: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.055: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.055: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.055: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.055: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.055: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.055: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.055: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.055: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.055: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.055: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.056: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.056: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.056: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.056: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.056: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.056: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.056: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.056: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.056: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.056: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.056: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.056: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.056: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.056: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.056: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.057: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.057: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.057: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.057: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.057: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.057: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.057: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.057: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.057: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.057: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.058: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.058: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.058: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.058: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.058: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.058: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.058: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.058: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.058: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.058: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.058: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.058: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.058: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.058: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.059: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.059: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.059: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.059: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.059: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.059: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.059: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.059: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.059: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.059: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.059: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.059: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.059: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.059: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.059: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.059: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.060: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.060: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.060: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.060: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.060: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.060: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.060: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.060: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.060: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.060: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.060: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.060: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.060: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.060: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.060: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.060: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.061: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.061: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.061: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.061: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.061: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.061: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.061: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.061: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.061: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.061: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.062: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.062: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.062: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.062: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.062: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.062: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.062: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.062: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.062: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.062: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.062: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.062: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.062: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.062: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.062: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.062: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.063: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.063: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.063: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.063: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.063: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.063: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.063: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.063: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.063: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.063: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.063: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.063: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.063: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.063: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.063: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.063: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.064: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.064: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.064: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.064: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.064: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.064: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.064: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.064: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.064: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.064: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.064: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.064: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.064: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.064: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.064: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.065: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.065: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.065: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.065: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.065: [vfs7552] CAPTURE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.065: [vfs7552] QUERY DATA READY entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.065: Sending vfs7552_is_image_ready
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.065: [vfs7552] QUERY DATA READY entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.065: Receiving 64 bytes
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.065: Got 6 bytes out of 64
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.065: [vfs7552] QUERY DATA READY completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.065: [vfs7552] CAPTURE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.065: [vfs7552] CAPTURE_NUM_STATES entering state 2
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.065: [vfs7552] REQUEST CHUNK entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.065: Sending vfs7552_read_image_chunk
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.066: [vfs7552] REQUEST CHUNK completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.066: [vfs7552] CAPTURE_NUM_STATES entering state 3
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.066: [vfs7552] CAPTURE_NUM_STATES entering state 2
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.066: [vfs7552] REQUEST CHUNK entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.066: Sending vfs7552_read_image_chunk
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.066: [vfs7552] REQUEST CHUNK completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.066: [vfs7552] CAPTURE_NUM_STATES entering state 3
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.067: [vfs7552] CAPTURE_NUM_STATES entering state 2
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.067: [vfs7552] REQUEST CHUNK entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.067: Sending vfs7552_read_image_chunk
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.067: [vfs7552] REQUEST CHUNK completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.067: [vfs7552] CAPTURE_NUM_STATES entering state 3
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.067: [vfs7552] CAPTURE_NUM_STATES entering state 4
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.067: Cleaning image
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.067: variance_after = 16
174s 
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.067: [vfs7552] CAPTURE_NUM_STATES completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.067: [vfs7552] DEACTIVATE_NUM_STATES entering state 0
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.077: [vfs7552] DEACTIVATE_NUM_STATES entering state 1
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.077: [vfs7552] STOP CAPTURE entering state 0
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.077: Sending vfs7552_cmd_04
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.078: [vfs7552] STOP CAPTURE entering state 1
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.078: Receiving 64 bytes
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.078: [vfs7552] STOP CAPTURE entering state 2
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.078: Sending vfs7552_cmd_52
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.078: [vfs7552] STOP CAPTURE entering state 3
174s (process:2479): libfprint-vfs7552-DEBUG: 05:03:05.078: Receiving 64 bytes
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.078: [vfs7552] STOP CAPTURE completed successfully
174s (process:2479): libfprint-SSM-DEBUG: 05:03:05.078: [vfs7552] DEACTIVATE_NUM_STATES completed successfully
174s (process:2479): libfprint-device-DEBUG: 05:03:05.078: Device reported finger status change: FP_FINGER_STATUS_NONE
174s (process:2479): libfprint-image_device-DEBUG: 05:03:05.078: Image device reported finger status: off
174s (process:2479): libfprint-image_device-DEBUG: 05:03:05.078: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
174s (process:2479): libfprint-image_device-DEBUG: 05:03:05.078: Deactivating image device
174s (process:2479): libfprint-image_device-DEBUG: 05:03:05.078: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
174s (process:2479): libfprint-image_device-DEBUG: 05:03:05.078: Image device deactivation completed
174s (process:2479): libfprint-image_device-DEBUG: 05:03:05.078: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
174s (process:2479): libfprint-device-DEBUG: 05:03:05.078: Device reported capture completion
174s (process:2479): libfprint-device-DEBUG: 05:03:05.078: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
174s (process:2479): libfprint-device-DEBUG: 05:03:05.078: Updated temperature model after 1.59 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2479): libfprint-image_device-DEBUG: 05:03:05.079: Image device close completed
174s (process:2479): libfprint-device-DEBUG: 05:03:05.079: Device reported close completion
174s (process:2479): libfprint-device-DEBUG: 05:03:05.079: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s (process:2479): libfprint-device-DEBUG: 05:03:05.079: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s ** (umockdev-run:2475): DEBUG: 05:03:05.165: umockdev.vala:154: Removing test bed /tmp/umockdev.0ZZI22
174s (umockdev-run:2475): GLib-DEBUG: 05:03:05.169: unsetenv() is not thread-safe and should not be used after threads are created
174s Comparing PNGs /tmp/libfprint-umockdev-test-d4ku2yvv/capture.png and /usr/share/installed-tests/libfprint-2/vfs7552/capture.png
174s PASS: libfprint-2/driver-vfs7552.test
174s Running test: libfprint-2/driver-nb1010.test
174s ** (umockdev-run:2488): DEBUG: 05:03:05.217: umockdev.vala:127: Created udev test bed /tmp/umockdev.RJSD22
174s ** (umockdev-run:2488): DEBUG: 05:03:05.218: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7
174s ** (umockdev-run:2488): DEBUG: 05:03:05.222: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1/1-7 (subsystem usb)
174s ** (umockdev-run:2488): DEBUG: 05:03:05.224: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.RJSD22/dev/bus/usb/001/003
174s ** (umockdev-run:2488): DEBUG: 05:03:05.224: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1
174s ** (umockdev-run:2488): DEBUG: 05:03:05.229: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0/usb1 (subsystem usb)
174s ** (umockdev-run:2488): DEBUG: 05:03:05.230: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.RJSD22/dev/bus/usb/001/001
174s ** (umockdev-run:2488): DEBUG: 05:03:05.230: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3/0000:02:00.0
174s ** (umockdev-run:2488): DEBUG: 05:03:05.233: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3/0000:02:00.0 (subsystem pci)
174s ** (umockdev-run:2488): DEBUG: 05:03:05.234: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:01.3
174s ** (umockdev-run:2488): DEBUG: 05:03:05.235: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:01.3 (subsystem pci)
174s (umockdev-run:2488): GLib-GIO-DEBUG: 05:03:05.237: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
174s (process:2492): libfprint-context-DEBUG: 05:03:05.300: Initializing FpContext (libfprint version 1.94.9+tod1)
174s (process:2492): libfprint-tod-DEBUG: 05:03:05.300: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
174s (process:2492): libfprint-context-DEBUG: 05:03:05.301: No driver found for USB device 1D6B:0002
174s (process:2492): libfprint-device-DEBUG: 05:03:05.301: Device reported probe completion
174s (process:2492): libfprint-device-DEBUG: 05:03:05.301: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s (process:2492): libfprint-device-DEBUG: 05:03:05.301: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.302: Image device open completed
174s (process:2492): libfprint-device-DEBUG: 05:03:05.302: Device reported open completion
174s (process:2492): libfprint-nb1010-DEBUG: 05:03:05.302: nb1010 Initialized
174s (process:2492): libfprint-device-DEBUG: 05:03:05.302: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s (process:2492): libfprint-device-DEBUG: 05:03:05.302: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2492): libfprint-device-DEBUG: 05:03:05.303: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.303: Activating image device
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.303: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.303: Image device activation completed
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.303: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.303: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
174s (process:2492): libfprint-SSM-DEBUG: 05:03:05.303: [nb1010] M_LOOP_NUM_STATES entering state 0
174s (process:2492): libfprint-device-DEBUG: 05:03:05.303: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2492): libfprint-nb1010-DEBUG: 05:03:05.303: nb1010 Activated
174s (process:2492): libfprint-SSM-DEBUG: 05:03:05.353: [nb1010] M_LOOP_NUM_STATES entering state 1
174s (process:2492): libfprint-SSM-DEBUG: 05:03:05.353: [nb1010] M_LOOP_NUM_STATES entering state 2
174s (process:2492): libfprint-SSM-DEBUG: 05:03:05.353: [nb1010] M_LOOP_NUM_STATES entering state 3
174s (process:2492): libfprint-device-DEBUG: 05:03:05.353: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.353: Image device reported finger status: on
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.353: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
174s (process:2492): libfprint-SSM-DEBUG: 05:03:05.354: [nb1010] M_LOOP_NUM_STATES entering state 4
174s (process:2492): libfprint-SSM-DEBUG: 05:03:05.355: [nb1010] M_LOOP_NUM_STATES entering state 5
174s (process:2492): libfprint-SSM-DEBUG: 05:03:05.381: [nb1010] M_LOOP_NUM_STATES entering state 6
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.381: Image device captured an image
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.382: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
174s (process:2492): libfprint-device-DEBUG: 05:03:05.382: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2492): libfprint-SSM-DEBUG: 05:03:05.382: [nb1010] M_LOOP_NUM_STATES completed successfully
174s (process:2492): libfprint-nb1010-DEBUG: 05:03:05.382: nb1010 ssm complete cb
174s (process:2492): libfprint-device-DEBUG: 05:03:05.382: Device reported finger status change: FP_FINGER_STATUS_NONE
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.382: Image device reported finger status: off
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.382: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.382: Deactivating image device
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.382: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.382: Image device deactivation completed
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.382: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
174s (process:2492): libfprint-nb1010-DEBUG: 05:03:05.382: nb1010 Deactivated
174s (process:2492): libfprint-image-DEBUG: 05:03:05.394: Minutiae scan completed in 0.011847 secs
174s (process:2492): libfprint-device-DEBUG: 05:03:05.394: Device reported capture completion
174s (process:2492): libfprint-device-DEBUG: 05:03:05.394: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
174s (process:2492): libfprint-device-DEBUG: 05:03:05.394: Updated temperature model after 0.09 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
174s (process:2492): libfprint-image_device-DEBUG: 05:03:05.394: Image device close completed
174s (process:2492): libfprint-device-DEBUG: 05:03:05.394: Device reported close completion
174s (process:2492): libfprint-nb1010-DEBUG: 05:03:05.394: nb1010 Deinitialized
174s (process:2492): libfprint-device-DEBUG: 05:03:05.394: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s (process:2492): libfprint-device-DEBUG: 05:03:05.394: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s ** (umockdev-run:2488): DEBUG: 05:03:05.467: umockdev.vala:154: Removing test bed /tmp/umockdev.RJSD22
174s (umockdev-run:2488): GLib-DEBUG: 05:03:05.470: unsetenv() is not thread-safe and should not be used after threads are created
174s Comparing PNGs /tmp/libfprint-umockdev-test-3qrhoytb/capture.png and /usr/share/installed-tests/libfprint-2/nb1010/capture.png
174s PASS: libfprint-2/driver-nb1010.test
174s Running test: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test
174s TAP version 14
174s # random seed: R02Sb87ff7a6a7ed071fc0e1c39338ce01cc
174s 1..14
174s # Start of device tests
174s # Start of async tests
174s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
174s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
174s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffabe82990, GType is 2929259691184
174s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
174s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
174s # libfprint-context-DEBUG: created
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
174s # 
174s # libfprint-device-DEBUG: Device reported probe completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
174s # 
174s # libfprint-device-DEBUG: Device reported open completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
174s # 
174s # libfprint-device-DEBUG: Device reported close completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s ok 1 /device/async/open
174s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
174s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
174s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffabe82990, GType is 2929259691184
174s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
174s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
174s # libfprint-context-DEBUG: created
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
174s # 
174s # libfprint-device-DEBUG: Device reported probe completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
174s # 
174s # libfprint-device-DEBUG: Device reported open completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
174s # 
174s # libfprint-device-DEBUG: Device reported close completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s ok 2 /device/async/close
174s # End of async tests
174s # Start of sync tests
174s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
174s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
174s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffabe82990, GType is 2929259691184
174s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
174s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
174s # libfprint-context-DEBUG: created
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
174s # 
174s # libfprint-device-DEBUG: Device reported probe completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
174s # 
174s # libfprint-device-DEBUG: Device reported open completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
174s # 
174s # libfprint-device-DEBUG: Device reported close completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s ok 3 /device/sync/open
174s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
174s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
174s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffabe82990, GType is 2929259691184
174s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
174s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
174s # libfprint-context-DEBUG: created
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
174s # 
174s # libfprint-device-DEBUG: Device reported probe completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
174s # 
174s # libfprint-device-DEBUG: Device reported open completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
174s # 
174s # libfprint-device-DEBUG: Device reported close completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s ok 4 /device/sync/close
174s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
174s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
174s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffabe82990, GType is 2929259691184
174s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
174s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
174s # libfprint-context-DEBUG: created
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
174s # 
174s # libfprint-device-DEBUG: Device reported probe completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
174s # 
174s # libfprint-device-DEBUG: Device reported open completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
174s # 
174s # libfprint-device-DEBUG: Device reported close completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s ok 5 /device/sync/get_driver
174s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
174s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
174s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffabe82990, GType is 2929259691184
174s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
174s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
174s # libfprint-context-DEBUG: created
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
174s # 
174s # libfprint-device-DEBUG: Device reported probe completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
174s # 
174s # libfprint-device-DEBUG: Device reported open completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
174s # 
174s # libfprint-device-DEBUG: Device reported close completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s ok 6 /device/sync/get_device_id
174s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
174s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
174s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffabe82990, GType is 2929259691184
174s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
174s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
174s # libfprint-context-DEBUG: created
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
174s # 
174s # libfprint-device-DEBUG: Device reported probe completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
174s # 
174s # libfprint-device-DEBUG: Device reported open completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
174s # 
174s # libfprint-device-DEBUG: Device reported close completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s ok 7 /device/sync/get_name
174s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
174s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
174s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffabe82990, GType is 2929259691184
174s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
174s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
174s # libfprint-context-DEBUG: created
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
174s # 
174s # libfprint-device-DEBUG: Device reported probe completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
174s # 
174s # libfprint-device-DEBUG: Device reported open completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
174s # 
174s # libfprint-device-DEBUG: Device reported close completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s ok 8 /device/sync/get_scan_type
174s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
174s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
174s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffabe82990, GType is 2929259691184
174s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
174s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
174s # libfprint-context-DEBUG: created
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
174s # 
174s # libfprint-device-DEBUG: Device reported probe completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
174s # 
174s # libfprint-device-DEBUG: Device reported open completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
174s # 
174s # libfprint-device-DEBUG: Device reported close completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s ok 9 /device/sync/get_nr_enroll_stages
174s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
174s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
174s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffabe82990, GType is 2929259691184
174s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
174s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
174s # libfprint-context-DEBUG: created
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
174s # 
174s # libfprint-device-DEBUG: Device reported probe completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
174s # 
174s # libfprint-device-DEBUG: Device reported open completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
174s # 
174s # libfprint-device-DEBUG: Device reported close completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s ok 10 /device/sync/supports_identify
174s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
174s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
174s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffabe82990, GType is 2929259691184
174s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
174s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
174s # libfprint-context-DEBUG: created
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
174s # 
174s # libfprint-device-DEBUG: Device reported probe completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
174s # 
174s # libfprint-device-DEBUG: Device reported open completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
174s # 
174s # libfprint-device-DEBUG: Device reported close completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s ok 11 /device/sync/supports_capture
174s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
174s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
174s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffabe82990, GType is 2929259691184
174s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
174s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
174s # libfprint-context-DEBUG: created
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
174s # 
174s # libfprint-device-DEBUG: Device reported probe completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
174s # 
174s # libfprint-device-DEBUG: Device reported open completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
174s # 
174s # libfprint-device-DEBUG: Device reported close completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s ok 12 /device/sync/has_storage
174s # Start of open tests
174s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
174s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
174s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffabe82990, GType is 2929259691184
174s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
174s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
174s # libfprint-context-DEBUG: created
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
174s # 
174s # libfprint-device-DEBUG: Device reported probe completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
174s # 
174s # libfprint-device-DEBUG: Device reported open completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
174s # 
174s # libfprint-device-DEBUG: Device reported close completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s ok 13 /device/sync/open/notify
174s # End of open tests
174s # Start of close tests
174s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
174s # libfprint-tod-DEBUG: Opening driver /usr/libexec/installed-tests/libfprint-2/tod-drivers/current/libdevice-fake-tod-driver.so
174s # libfprint-tod-DEBUG: Found TOD entry point symbol 0x3ffabe82990, GType is 2929259691184
174s # libfprint-tod-DEBUG: Loading driver fake_test_dev_tod_current (Virtual device for debugging)
174s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_FAKE_DEVICE, yes
174s # libfprint-context-DEBUG: created
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
174s # 
174s # libfprint-device-DEBUG: Device reported probe completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
174s # 
174s # libfprint-device-DEBUG: Device reported open completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s # libfprint-fake_test_dev_tod_current-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
174s # 
174s # libfprint-device-DEBUG: Device reported close completion
174s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s ok 14 /device/sync/close/notify
174s # End of close tests
174s # End of sync tests
174s # End of device tests
174s PASS: libfprint-2/tod-fp-device-tod-fake_test_dev_tod_current.test
174s Running test: libfprint-2/driver-egismoc.test
174s ** (umockdev-run:2533): DEBUG: 05:03:05.525: umockdev.vala:127: Created udev test bed /tmp/umockdev.86K112
174s ** (umockdev-run:2533): DEBUG: 05:03:05.525: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5
174s ** (umockdev-run:2533): DEBUG: 05:03:05.526: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb)
174s ** (umockdev-run:2533): DEBUG: 05:03:05.528: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.86K112/dev/bus/usb/003/012
174s ** (umockdev-run:2533): DEBUG: 05:03:05.528: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3
174s ** (umockdev-run:2533): DEBUG: 05:03:05.529: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb)
174s ** (umockdev-run:2533): DEBUG: 05:03:05.530: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.86K112/dev/bus/usb/003/001
174s ** (umockdev-run:2533): DEBUG: 05:03:05.530: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0
174s ** (umockdev-run:2533): DEBUG: 05:03:05.530: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
174s (process:2537): libfprint-context-DEBUG: 05:03:05.589: Initializing FpContext (libfprint version 1.94.9+tod1)
174s (process:2537): libfprint-tod-DEBUG: 05:03:05.589: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.590: 52338927: ../libfprint/drivers/egismoc/egismoc.c:1597
174s (process:2537): libfprint-context-DEBUG: 05:03:05.590: No driver found for USB device 1D6B:0002
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.590: egismoc_probe enter --> 
174s (process:2537): libfprint-device-DEBUG: 05:03:05.591: Device reported probe completion
174s (process:2537): libfprint-device-DEBUG: 05:03:05.591: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.591: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.592: Opening device
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.592: [egismoc] DEV_INIT_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.592: [egismoc] DEV_INIT_STATES entering state 1
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.593: [egismoc] DEV_INIT_STATES entering state 2
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.593: [egismoc] DEV_INIT_STATES entering state 3
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.594: [egismoc] DEV_INIT_STATES entering state 4
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.594: [egismoc] DEV_INIT_STATES entering state 5
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.594: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.594: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.594: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.594: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.595: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.595: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.595: Firmware version callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.595: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.595: Device firmware version is 9050.1.1.81
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.595: [egismoc] DEV_INIT_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.595: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.595: Device reported open completion
174s (process:2537): libfprint-device-DEBUG: 05:03:05.595: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.595: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.595: List
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.595: [egismoc] LIST_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.595: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.595: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.595: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.595: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.596: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.596: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.596: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.596: Device fingerprint 1: FP1-20231016-1-AAA9163E-root
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.596: Device fingerprint 2: FP1-20231016-2-5102A0A3-root
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.596: Device fingerprint 3: FP1-20231016-3-5159A026-root
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.596: Device fingerprint 4: FP1-20231016-4-A25C1212-root
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.596: Device fingerprint 5: FP1-20231016-5-EC893AA9-root
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.596: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN(
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.596: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.596: Number of currently enrolled fingerprints on the device is 7
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.596: [egismoc] LIST_STATES entering state 1
174s (process:2537): libfprint-device-DEBUG: 05:03:05.596: Device reported listing completion
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.596: [egismoc] LIST_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.596: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.596: Completing action FPI_DEVICE_ACTION_LIST in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.596: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.596: Clear storage
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.596: [egismoc] DELETE_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.596: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.596: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.596: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.596: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.597: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.597: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.597: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.597: Device fingerprint 1: FP1-20231016-1-AAA9163E-root
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.597: Device fingerprint 2: FP1-20231016-2-5102A0A3-root
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.597: Device fingerprint 3: FP1-20231016-3-5159A026-root
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.597: Device fingerprint 4: FP1-20231016-4-A25C1212-root
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.597: Device fingerprint 5: FP1-20231016-5-EC893AA9-root
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.597: Device fingerprint 6: \u0006\u001d\xcbc$ir%\xa22U֨\o\xff\x8ddY\x84\u0003\xbac\xcfO\xde\xc2!L\u001eN(
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.597: Device fingerprint 7: \xd7pܖsT3\xf6>\xd9\u0002"/[\xf8\u0017Iqpz\u000c\xfa,M\xdfm5\u007fq\xc6\xdew
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.597: Number of currently enrolled fingerprints on the device is 7
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.597: [egismoc] DELETE_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.597: Get delete command
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.597: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.597: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.597: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.597: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.598: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.598: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.598: Delete callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.598: Response prefix valid: yes
174s (process:2537): libfprint-device-DEBUG: 05:03:05.598: Device reported deletion completion
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.598: [egismoc] DELETE_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.598: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.598: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.598: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.598: List
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.598: [egismoc] LIST_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.598: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.598: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.598: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.598: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.599: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.599: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.599: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.599: Number of currently enrolled fingerprints on the device is 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.599: [egismoc] LIST_STATES entering state 1
174s (process:2537): libfprint-device-DEBUG: 05:03:05.599: Device reported listing completion
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.599: [egismoc] LIST_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.599: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.599: Completing action FPI_DEVICE_ACTION_LIST in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.599: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2537): libfprint-device-DEBUG: 05:03:05.599: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.599: Enroll
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.599: [egismoc] ENROLL_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.599: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.599: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.599: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.599: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.600: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.600: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.600: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.600: Number of currently enrolled fingerprints on the device is 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.600: [egismoc] ENROLL_STATES entering state 1
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.600: [egismoc] ENROLL_STATES entering state 2
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.600: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.600: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.600: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.600: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.601: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.601: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.601: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.601: [egismoc] ENROLL_STATES entering state 3
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.601: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.601: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.601: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.601: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.602: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.602: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.602: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.602: [egismoc] ENROLL_STATES entering state 4
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.602: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.602: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.602: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.602: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.602: [egismoc] ENROLL_STATES entering state 5
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.602: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.602: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.602: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.603: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.603: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.603: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.603: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.603: [egismoc] ENROLL_STATES entering state 6
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.603: Get check command
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.603: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.603: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.603: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.604: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.604: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.604: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.604: Enroll check callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.604: Response suffix valid: yes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.604: [egismoc] ENROLL_STATES entering state 7
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.604: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.604: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.604: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.605: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.605: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.605: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.605: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.605: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.605: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.605: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.605: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.605: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.606: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.606: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.606: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.606: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.606: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.606: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.606: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.606: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.607: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.607: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.607: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.607: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.607: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.607: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.607: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.607: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.607: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.607: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.607: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.607: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.607: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.608: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.608: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.608: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.608: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.608: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.608: Partial capture successful. Please touch the sensor again (1/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.608: Device reported enroll progress, reported 1 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.608: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.608: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.608: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.608: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.608: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.609: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.609: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.609: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.609: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.609: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.609: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.609: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.609: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.610: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.610: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.610: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.610: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.610: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.610: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.610: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.610: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.610: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.610: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.610: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.610: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.610: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.611: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.611: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.611: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.611: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.611: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.611: Partial capture successful. Please touch the sensor again (2/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.611: Device reported enroll progress, reported 2 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.611: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.611: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.611: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.611: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.611: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.611: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.611: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.611: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.611: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.611: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.611: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.611: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.612: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.612: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.612: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.612: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.612: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.612: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.612: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.613: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.613: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.613: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.613: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.613: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.613: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.613: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.613: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.613: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.613: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.613: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.613: Response suffix valid: NO
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.613: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.613: Response suffix valid: yes
174s (process:2537): libfprint-device-DEBUG: 05:03:05.613: Device reported enroll progress, reported 2 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.613: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.613: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.613: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.613: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.614: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.614: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.614: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.614: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.614: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.614: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.614: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.614: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.614: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.615: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.615: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.615: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.615: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.615: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.615: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.615: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.615: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.615: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.615: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.615: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.615: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.616: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.616: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.616: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.616: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.616: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.616: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.616: Partial capture successful. Please touch the sensor again (3/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.616: Device reported enroll progress, reported 3 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.616: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.616: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.616: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.616: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.616: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.617: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.617: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.617: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.617: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.617: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.617: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.617: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.617: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.618: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.618: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.618: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.618: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.618: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.618: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.618: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.618: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.618: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.618: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.618: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.618: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.618: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.619: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.619: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.619: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.619: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.619: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.619: Partial capture successful. Please touch the sensor again (4/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.619: Device reported enroll progress, reported 4 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.619: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.619: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.619: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.619: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.619: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.620: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.620: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.620: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.620: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.620: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.620: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.620: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.620: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.621: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.621: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.621: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.621: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.621: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.621: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.621: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.621: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.621: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.621: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.621: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.621: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.621: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.622: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.622: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.622: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.622: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.622: Response suffix valid: NO
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.622: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.622: Response suffix valid: yes
174s (process:2537): libfprint-device-DEBUG: 05:03:05.622: Device reported enroll progress, reported 4 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.622: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.622: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.622: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.622: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.622: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.623: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.623: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.623: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.623: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.623: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.623: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.623: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.623: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.624: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.624: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.624: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.624: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.624: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.624: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.624: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.624: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.624: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.624: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.624: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.624: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.624: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.625: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.625: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.625: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.625: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.625: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.625: Partial capture successful. Please touch the sensor again (5/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.625: Device reported enroll progress, reported 5 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.625: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.625: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.625: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.625: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.625: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.626: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.626: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.626: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.626: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.626: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.626: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.626: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.626: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.626: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.626: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.626: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.626: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.626: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.626: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.627: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.627: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.627: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.627: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.627: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.627: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.627: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.627: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.627: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.627: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.627: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.627: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.627: Partial capture successful. Please touch the sensor again (6/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.627: Device reported enroll progress, reported 6 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.627: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.627: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.627: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.627: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.628: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.628: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.628: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.628: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.628: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.628: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.628: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.628: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.628: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.629: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.629: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.629: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.629: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.629: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.629: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.629: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.629: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.629: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.629: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.629: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.629: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.630: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.630: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.630: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.630: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.630: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.630: Response suffix valid: NO
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.630: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.630: Response suffix valid: yes
174s (process:2537): libfprint-device-DEBUG: 05:03:05.630: Device reported enroll progress, reported 6 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.630: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.630: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.630: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.630: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.630: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.631: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.631: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.631: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.631: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.631: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.631: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.631: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.631: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.632: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.632: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.632: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.632: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.632: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.632: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.632: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.632: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.632: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.632: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.632: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.632: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.632: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.633: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.633: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.633: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.633: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.633: Response suffix valid: NO
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.633: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.633: Response suffix valid: yes
174s (process:2537): libfprint-device-DEBUG: 05:03:05.633: Device reported enroll progress, reported 6 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.633: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.633: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.633: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.633: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.633: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.634: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.634: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.634: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.634: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.634: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.634: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.634: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.634: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.634: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.634: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.634: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.634: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.634: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.634: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.635: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.635: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.635: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.635: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.635: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.635: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.635: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.636: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.636: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.636: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.636: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.636: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.636: Partial capture successful. Please touch the sensor again (7/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.636: Device reported enroll progress, reported 7 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.636: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.636: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.636: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.636: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.636: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.636: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.636: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.636: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.636: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.636: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.636: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.636: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.637: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.637: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.637: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.637: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.637: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.637: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.637: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.638: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.638: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.638: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.638: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.638: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.638: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.638: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.638: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.638: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.638: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.638: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.638: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.638: Partial capture successful. Please touch the sensor again (8/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.638: Device reported enroll progress, reported 8 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.638: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.638: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.638: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.638: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.639: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.639: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.639: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.639: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.639: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.639: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.639: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.639: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.640: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.640: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.640: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.640: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.640: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.640: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.640: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.640: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.640: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.640: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.640: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.640: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.640: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.641: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.641: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.641: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.641: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.641: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.641: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.641: Partial capture successful. Please touch the sensor again (9/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.641: Device reported enroll progress, reported 9 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.641: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.641: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.641: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.641: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.642: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.642: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.642: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.642: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.642: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.642: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.642: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.642: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.642: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.642: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.642: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.642: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.642: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.642: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.642: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.643: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.643: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.643: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.643: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.643: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.643: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.643: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.643: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.643: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.643: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.643: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.643: Response suffix valid: NO
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.643: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.643: Response suffix valid: yes
174s (process:2537): libfprint-device-DEBUG: 05:03:05.643: Device reported enroll progress, reported 9 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.643: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.643: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.643: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.643: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.644: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.644: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.644: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.644: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.644: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.644: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.644: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.644: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.645: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.645: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.645: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.645: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.645: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.645: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.645: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.645: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.645: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.645: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.645: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.645: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.645: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.646: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.646: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.646: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.646: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.646: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.646: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.646: Partial capture successful. Please touch the sensor again (10/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.646: Device reported enroll progress, reported 10 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.646: [egismoc] ENROLL_STATES entering state 12
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.646: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.646: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.646: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.646: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.647: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.647: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.647: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.647: [egismoc] ENROLL_STATES entering state 13
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.647: New fingerprint ID: FP1-00000000-2-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.647: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.647: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.647: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.647: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.648: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.648: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.648: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.648: [egismoc] ENROLL_STATES entering state 14
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.648: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.648: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.648: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.648: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.648: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.648: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.648: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.648: [egismoc] ENROLL_STATES entering state 15
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.648: Enrollment was successful!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.648: Device reported enroll completion
174s (process:2537): libfprint-device-DEBUG: 05:03:05.648: Device reported finger status change: FP_FINGER_STATUS_NONE
174s (process:2537): libfprint-device-DEBUG: 05:03:05.648: Print for finger FP_FINGER_LEFT_INDEX enrolled
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.648: [egismoc] ENROLL_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.648: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.648: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.648: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.648: List
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.648: [egismoc] LIST_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.648: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.648: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.648: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.649: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.649: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.649: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.649: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.649: Device fingerprint 1: FP1-00000000-2-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.649: Number of currently enrolled fingerprints on the device is 1
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.649: [egismoc] LIST_STATES entering state 1
174s (process:2537): libfprint-device-DEBUG: 05:03:05.649: Device reported listing completion
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.649: [egismoc] LIST_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.649: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.649: Completing action FPI_DEVICE_ACTION_LIST in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.649: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-device-DEBUG: 05:03:05.649: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.649: Identify or Verify
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.649: [egismoc] IDENTIFY_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.649: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.649: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.649: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.650: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.650: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.650: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.650: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.650: Device fingerprint 1: FP1-00000000-2-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.650: Number of currently enrolled fingerprints on the device is 1
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.650: [egismoc] IDENTIFY_STATES entering state 1
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.650: [egismoc] IDENTIFY_STATES entering state 2
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.650: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.650: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.650: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.651: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.651: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.651: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.651: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.651: [egismoc] IDENTIFY_STATES entering state 3
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.651: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.651: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.651: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.652: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.652: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.652: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.652: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.652: [egismoc] IDENTIFY_STATES entering state 4
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.652: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.652: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.652: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.652: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.652: [egismoc] IDENTIFY_STATES entering state 5
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.652: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.652: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.652: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.653: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.653: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.653: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.653: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.653: [egismoc] IDENTIFY_STATES entering state 6
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.653: Get check command
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.653: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.653: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.653: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.654: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.654: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.654: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.654: Identify check callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.654: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.654: Identify successful for: FP1-00000000-2-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.654: Verifying against: FP1-00000000-2-00000000-nobody
174s (process:2537): libfprint-device-DEBUG: 05:03:05.654: Device reported verify result
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.654: [egismoc] IDENTIFY_STATES entering state 7
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.654: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.654: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.654: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.655: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.655: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.655: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.655: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.655: [egismoc] IDENTIFY_STATES entering state 8
174s (process:2537): libfprint-device-DEBUG: 05:03:05.655: Device reported verify completion
174s (process:2537): libfprint-device-DEBUG: 05:03:05.655: Device reported finger status change: FP_FINGER_STATUS_NONE
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.655: [egismoc] IDENTIFY_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.655: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.655: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.655: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-device-DEBUG: 05:03:05.655: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.655: Identify or Verify
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.655: [egismoc] IDENTIFY_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.655: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.655: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.655: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.656: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.656: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.656: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.656: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.656: Device fingerprint 1: FP1-00000000-2-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.656: Number of currently enrolled fingerprints on the device is 1
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.656: [egismoc] IDENTIFY_STATES entering state 1
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.656: [egismoc] IDENTIFY_STATES entering state 2
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.656: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.656: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.656: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.657: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.657: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.657: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.657: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.657: [egismoc] IDENTIFY_STATES entering state 3
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.657: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.657: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.657: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.658: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.658: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.658: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.658: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.658: [egismoc] IDENTIFY_STATES entering state 4
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.658: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.658: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.659: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.659: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.659: [egismoc] IDENTIFY_STATES entering state 5
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.659: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.659: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.659: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.659: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.659: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.659: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.659: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.659: [egismoc] IDENTIFY_STATES entering state 6
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.659: Get check command
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.659: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.659: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.659: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.660: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.660: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.660: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.660: Identify check callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.660: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.660: Identify successful for: FP1-00000000-2-00000000-nobody
174s (process:2537): libfprint-device-DEBUG: 05:03:05.660: Device reported identify result
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.660: [egismoc] IDENTIFY_STATES entering state 7
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.660: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.660: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.660: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.661: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.661: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.661: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.661: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.661: [egismoc] IDENTIFY_STATES entering state 8
174s (process:2537): libfprint-device-DEBUG: 05:03:05.661: Device reported identify completion
174s (process:2537): libfprint-device-DEBUG: 05:03:05.661: Device reported finger status change: FP_FINGER_STATUS_NONE
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.661: [egismoc] IDENTIFY_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.661: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.661: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.661: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-device-DEBUG: 05:03:05.662: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.662: Enroll
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.662: [egismoc] ENROLL_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.662: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.662: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.662: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.662: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.662: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.663: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.663: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.663: Device fingerprint 1: FP1-00000000-2-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.663: Number of currently enrolled fingerprints on the device is 1
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.663: [egismoc] ENROLL_STATES entering state 1
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.663: [egismoc] ENROLL_STATES entering state 2
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.663: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.663: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.663: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.663: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.663: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.663: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.663: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.663: [egismoc] ENROLL_STATES entering state 3
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.663: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.663: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.663: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.664: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.664: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.664: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.664: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.664: [egismoc] ENROLL_STATES entering state 4
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.664: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.664: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.664: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.665: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.665: [egismoc] ENROLL_STATES entering state 5
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.665: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.665: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.665: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.665: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.665: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.665: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.665: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.665: [egismoc] ENROLL_STATES entering state 6
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.665: Get check command
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.665: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.665: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.665: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.665: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.666: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.666: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.666: Enroll check callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.666: Response suffix valid: NO
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.666: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.666: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.666: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.666: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL
174s (process:2537): libfprint-device-DEBUG: 05:03:05.666: Device reported enroll completion
174s (process:2537): libfprint-device-DEBUG: 05:03:05.666: Device reported finger status change: FP_FINGER_STATUS_NONE
174s (process:2537): libfprint-device-DEBUG: 05:03:05.666: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.666: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.666: List
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.666: [egismoc] LIST_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.666: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.666: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.666: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.666: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.667: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.667: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.667: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.667: Device fingerprint 1: FP1-00000000-2-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.667: Number of currently enrolled fingerprints on the device is 1
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.667: [egismoc] LIST_STATES entering state 1
174s (process:2537): libfprint-device-DEBUG: 05:03:05.667: Device reported listing completion
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.667: [egismoc] LIST_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.667: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.667: Completing action FPI_DEVICE_ACTION_LIST in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.667: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-device-DEBUG: 05:03:05.667: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.667: Enroll
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.667: [egismoc] ENROLL_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.667: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.667: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.667: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.667: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.667: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.667: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.667: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.667: Device fingerprint 1: FP1-00000000-2-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.667: Number of currently enrolled fingerprints on the device is 1
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.667: [egismoc] ENROLL_STATES entering state 1
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.668: [egismoc] ENROLL_STATES entering state 2
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.668: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.668: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.668: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.668: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.668: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.668: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.668: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.668: [egismoc] ENROLL_STATES entering state 3
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.668: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.668: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.668: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.669: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.669: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.669: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.669: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.669: [egismoc] ENROLL_STATES entering state 4
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.669: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.669: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.669: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.669: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.669: [egismoc] ENROLL_STATES entering state 5
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.669: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.669: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.669: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.670: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.670: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.670: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.670: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.670: [egismoc] ENROLL_STATES entering state 6
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.670: Get check command
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.670: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.670: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.670: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.670: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.670: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.670: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.670: Enroll check callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.670: Response suffix valid: yes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.670: [egismoc] ENROLL_STATES entering state 7
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.670: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.671: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.671: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.671: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.671: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.671: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.671: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.671: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.671: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.671: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.671: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.672: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.672: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.672: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.672: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.672: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.672: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.672: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.672: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.672: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.673: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.673: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.673: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.673: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.673: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.673: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.673: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.673: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.673: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.673: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.673: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.673: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.673: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.674: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.674: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.674: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.674: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.674: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.674: Partial capture successful. Please touch the sensor again (1/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.674: Device reported enroll progress, reported 1 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.674: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.674: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.674: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.674: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.674: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.675: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.675: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.675: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.675: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.675: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.675: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.675: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.675: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.675: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.675: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.675: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.675: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.675: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.675: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.675: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.675: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.675: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.675: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.675: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.675: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.676: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.676: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.676: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.676: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.676: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.676: Response suffix valid: NO
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.676: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.676: Response suffix valid: yes
174s (process:2537): libfprint-device-DEBUG: 05:03:05.676: Device reported enroll progress, reported 1 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.676: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.676: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.676: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.676: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.676: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.677: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.677: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.677: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.677: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.677: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.677: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.677: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.677: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.678: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.678: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.678: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.678: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.678: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.678: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.678: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.678: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.678: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.678: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.678: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.678: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.679: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.679: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.679: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.679: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.679: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.679: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.679: Partial capture successful. Please touch the sensor again (2/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.679: Device reported enroll progress, reported 2 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.679: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.679: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.679: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.679: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.679: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.680: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.680: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.680: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.680: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.680: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.680: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.680: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.680: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.681: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.681: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.681: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.681: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.681: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.681: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.681: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.681: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.681: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.681: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.681: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.681: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.682: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.682: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.682: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.682: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.682: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.682: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.682: Partial capture successful. Please touch the sensor again (3/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.682: Device reported enroll progress, reported 3 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.682: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.682: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.682: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.682: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.682: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.683: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.683: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.683: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.683: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.683: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.683: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.683: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.683: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.683: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.683: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.683: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.683: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.683: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.683: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.684: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.684: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.684: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.684: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.684: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.684: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.684: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.685: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.685: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.685: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.685: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.685: Response suffix valid: NO
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.685: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.685: Response suffix valid: yes
174s (process:2537): libfprint-device-DEBUG: 05:03:05.685: Device reported enroll progress, reported 3 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.685: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.685: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.685: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.685: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.685: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.685: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.685: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.685: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.685: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.685: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.685: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.685: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.686: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.686: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.686: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.686: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.686: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.686: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.686: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.687: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.687: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.687: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.687: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.687: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.687: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.687: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.688: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.688: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.688: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.688: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.688: Response suffix valid: NO
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.688: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.688: Response suffix valid: yes
174s (process:2537): libfprint-device-DEBUG: 05:03:05.688: Device reported enroll progress, reported 3 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.688: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.688: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.688: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.688: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.688: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.688: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.688: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.688: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.688: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.688: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.688: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.688: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.689: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.689: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.689: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.689: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.689: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.689: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.689: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.690: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.690: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.690: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.690: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.690: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.690: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.690: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.690: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.690: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.690: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.690: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.690: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.690: Partial capture successful. Please touch the sensor again (4/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.690: Device reported enroll progress, reported 4 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.690: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.690: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.690: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.690: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.691: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.691: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.691: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.691: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.691: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.691: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.691: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.691: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.692: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.692: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.692: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.692: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.692: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.692: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.692: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.692: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.692: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.692: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.692: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.692: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.692: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.693: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.693: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.693: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.693: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.693: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.693: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.693: Partial capture successful. Please touch the sensor again (5/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.693: Device reported enroll progress, reported 5 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.693: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.693: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.693: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.693: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.694: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.694: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.694: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.694: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.694: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.694: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.694: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.694: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.695: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.695: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.695: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.695: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.695: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.695: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.695: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.695: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.695: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.695: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.695: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.695: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.695: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.696: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.696: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.696: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.696: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.696: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.696: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.696: Partial capture successful. Please touch the sensor again (6/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.696: Device reported enroll progress, reported 6 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.696: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.696: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.696: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.696: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.697: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.697: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.697: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.697: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.697: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.697: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.697: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.697: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.697: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.698: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.698: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.698: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.698: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.698: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.698: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.698: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.698: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.698: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.698: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.698: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.698: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.699: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.699: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.699: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.699: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.699: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.699: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.699: Partial capture successful. Please touch the sensor again (7/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.699: Device reported enroll progress, reported 7 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.699: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.699: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.699: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.699: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.699: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.700: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.700: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.700: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.700: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.700: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.700: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.700: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.700: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.701: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.701: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.701: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.701: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.701: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.701: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.701: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.701: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.701: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.701: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.701: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.701: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.701: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.702: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.702: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.702: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.702: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.702: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.702: Partial capture successful. Please touch the sensor again (8/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.702: Device reported enroll progress, reported 8 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.702: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.702: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.702: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.702: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.702: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.703: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.703: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.703: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.703: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.703: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.703: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.703: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.703: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.704: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.704: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.704: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.704: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.704: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.704: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.704: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.704: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.704: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.704: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.704: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.704: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.705: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.705: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.705: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.705: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.705: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.705: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.705: Partial capture successful. Please touch the sensor again (9/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.705: Device reported enroll progress, reported 9 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.705: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.705: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.705: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.705: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.705: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.706: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.706: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.706: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.706: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.706: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.706: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.706: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.706: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.707: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.707: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.707: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.707: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.707: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.707: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.707: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.707: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.707: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.707: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.707: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.707: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.707: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.708: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.708: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.708: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.708: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.708: Response suffix valid: NO
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.708: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.708: Response suffix valid: yes
174s (process:2537): libfprint-device-DEBUG: 05:03:05.708: Device reported enroll progress, reported 9 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.708: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.708: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.708: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.708: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.708: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.709: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.709: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.709: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.709: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.709: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.709: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.709: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.709: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.710: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.710: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.710: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.710: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.710: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.710: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.710: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.710: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.710: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.710: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.710: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.710: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.710: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.711: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.711: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.711: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.711: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.711: Response suffix valid: NO
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.711: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.711: Response suffix valid: yes
174s (process:2537): libfprint-device-DEBUG: 05:03:05.711: Device reported enroll progress, reported 9 of 10 have been completed
174s listing - device should have prints
174s clear device storage
174s clear done
174s listing - device should be empty
174s enrolling
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 1, <FPrint.Print object at 0x3ff8b40fcc0 (FpPrint at 0x1e275d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 2, <FPrint.Print object at 0x3ff8b40fcc0 (FpPrint at 0x1e275d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 2, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 3, <FPrint.Print object at 0x3ff8b40fcc0 (FpPrint at 0x1e275d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 4, <FPrint.Print object at 0x3ff8b40fcc0 (FpPrint at 0x1e275d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 4, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 5, <FPrint.Print object at 0x3ff8b40fcc0 (FpPrint at 0x1e275d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 6, <FPrint.Print object at 0x3ff8b40fcc0 (FpPrint at 0x1e275d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 7, <FPrint.Print object at 0x3ff8b40fcc0 (FpPrint at 0x1e275d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 8, <FPrint.Print object at 0x3ff8b40fcc0 (FpPrint at 0x1e275d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 9, <FPrint.Print object at 0x3ff8b40fcc0 (FpPrint at 0x1e275d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 10, <FPrint.Print object at 0x3ff8b40fcc0 (FpPrint at 0x1e275d0)>, None, None)
174s enroll done
174s listing - device should have 1 print
174s verifying
174s verify done
174s async identifying
174s indentification_done:  <FPrint.Print object at 0x3ff8b412ec0 (FpPrint at 0x1e2ece0)> <FPrint.Print object at 0x3ff8b412f00 (FpPrint at 0x1e380e0)>
174s try to enroll duplicate
174s duplicate enroll attempt done
174s listing - device should still only have 1 print
174s enroll new finger
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 1, <FPrint.Print object at 0x3ff8b413680 (FpPrint at 0x1e3b090)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 1, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 2, <FPrint.Print object at 0x3ff8b413680 (FpPrint at 0x1e3b090)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 3, <FPrint.Print object at 0x3ff8b413680 (FpPrint at 0x1e3b090)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 3, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 4, <FPrint.Print object at 0x3ff8b413680 (FpPrint at 0x1e3b090)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 5, <FPrint.Print object at 0x3ff8b413680 (FpPrint at 0x1e3b090)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 6, <FPrint.Print object at 0x3ff8b413680 (FpPrint at 0x1e3b090)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 7, <FPrint.Print object at 0x3ff8b413680 (FpPrint at 0x1e3b090)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 8, <FPrint.Print object at 0x3ff8b413680 (FpPrint at 0x1e3b090)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 9, <FPrint.Print object at 0x3ff8b413680 (FpPrint at 0x1e3b090)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>(process:2537): libfprint-SSM-DEBUG: 05:03:05.711: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.711: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.711: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.711: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.711: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.712: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.712: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.712: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.712: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.712: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.712: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.712: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.712: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.712: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.712: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.712: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.712: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.712: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.712: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.713: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.713: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.713: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.713: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.713: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.713: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.713: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.713: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.713: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.713: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.713: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.713: Response suffix valid: NO
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.713: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.713: Response suffix valid: yes
174s (process:2537): libfprint-device-DEBUG: 05:03:05.713: Device reported enroll progress, reported 9 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.713: [egismoc] ENROLL_STATES entering state 8
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.713: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.713: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.713: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.714: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.714: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.714: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.714: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.714: [egismoc] ENROLL_STATES entering state 9
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.714: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.714: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.714: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.715: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.715: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.715: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.715: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.715: [egismoc] ENROLL_STATES entering state 10
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.715: Wait for finger on sensor
174s (process:2537): libfprint-device-DEBUG: 05:03:05.715: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.715: Finger on sensor callback
174s (process:2537): libfprint-device-DEBUG: 05:03:05.715: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.715: [egismoc] ENROLL_STATES entering state 11
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.715: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.715: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.715: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.716: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.716: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.716: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.716: Read capture callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.716: Response prefix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.716: Response suffix valid: yes
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.716: Partial capture successful. Please touch the sensor again (10/10)
174s (process:2537): libfprint-device-DEBUG: 05:03:05.716: Device reported enroll progress, reported 10 of 10 have been completed
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.716: [egismoc] ENROLL_STATES entering state 12
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.716: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.716: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.716: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.716: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.717: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.717: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.717: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.717: [egismoc] ENROLL_STATES entering state 13
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.717: New fingerprint ID: FP1-00000000-7-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.717: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.717: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.717: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.717: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.717: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.717: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.717: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.717: [egismoc] ENROLL_STATES entering state 14
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.717: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.717: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.717: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.718: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.718: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.718: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.718: Task SSM next state callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.718: [egismoc] ENROLL_STATES entering state 15
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.718: Enrollment was successful!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.718: Device reported enroll completion
174s (process:2537): libfprint-device-DEBUG: 05:03:05.718: Device reported finger status change: FP_FINGER_STATUS_NONE
174s (process:2537): libfprint-device-DEBUG: 05:03:05.718: Print for finger FP_FINGER_RIGHT_INDEX enrolled
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.718: [egismoc] ENROLL_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.718: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.718: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.718: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.718: List
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.718: [egismoc] LIST_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.718: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.718: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.718: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.718: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.719: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.719: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.719: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.719: Device fingerprint 1: FP1-00000000-2-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.719: Device fingerprint 2: FP1-00000000-7-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.719: Number of currently enrolled fingerprints on the device is 2
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.719: [egismoc] LIST_STATES entering state 1
174s (process:2537): libfprint-device-DEBUG: 05:03:05.719: Device reported listing completion
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.719: [egismoc] LIST_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.719: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.719: Completing action FPI_DEVICE_ACTION_LIST in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.719: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.719: Delete
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.719: [egismoc] DELETE_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.719: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.719: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.719: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.719: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.720: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: Device fingerprint 1: FP1-00000000-2-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: Device fingerprint 2: FP1-00000000-7-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: Number of currently enrolled fingerprints on the device is 2
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.720: [egismoc] DELETE_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: Get delete command
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody)
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.720: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.720: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.720: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: Delete callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: Response prefix valid: yes
174s (process:2537): libfprint-device-DEBUG: 05:03:05.720: Device reported deletion completion
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.720: [egismoc] DELETE_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.720: Completing action FPI_DEVICE_ACTION_DELETE in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.720: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: List
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.720: [egismoc] LIST_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.720: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.720: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.721: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.721: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.721: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.721: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.721: Device fingerprint 1: FP1-00000000-7-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.721: Number of currently enrolled fingerprints on the device is 1
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.721: [egismoc] LIST_STATES entering state 1
174s (process:2537): libfprint-device-DEBUG: 05:03:05.721: Device reported listing completion
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.721: [egismoc] LIST_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.721: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.721: Completing action FPI_DEVICE_ACTION_LIST in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.721: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.721: Clear storage
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.721: [egismoc] DELETE_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.721: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.721: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.721: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.721: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.722: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.722: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.722: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.722: Device fingerprint 1: FP1-00000000-7-00000000-nobody
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.722: Number of currently enrolled fingerprints on the device is 1
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.722: [egismoc] DELETE_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.722: Get delete command
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.722: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.722: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.722: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.722: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.722: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.722: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.722: Delete callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.722: Response prefix valid: yes
174s (process:2537): libfprint-device-DEBUG: 05:03:05.722: Device reported deletion completion
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.722: [egismoc] DELETE_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.722: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.722: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.722: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.722: List
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.722: [egismoc] LIST_STATES entering state 0
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.722: Execute command and get response
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.722: Get check bytes
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.722: [egismoc] CMD_STATES entering state 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.722: [egismoc] CMD_STATES entering state 1
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.723: Command receive callback
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.723: [egismoc] CMD_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.723: List callback
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.723: Number of currently enrolled fingerprints on the device is 0
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.723: [egismoc] LIST_STATES entering state 1
174s (process:2537): libfprint-device-DEBUG: 05:03:05.723: Device reported listing completion
174s (process:2537): libfprint-SSM-DEBUG: 05:03:05.723: [egismoc] LIST_STATES completed successfully
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.723: Task SSM done
174s (process:2537): libfprint-device-DEBUG: 05:03:05.723: Completing action FPI_DEVICE_ACTION_LIST in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.723: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.723: Closing device
174s (process:2537): libfprint-egismoc-DEBUG: 05:03:05.723: Cancel
174s (process:2537): libfprint-device-DEBUG: 05:03:05.723: Device reported close completion
174s (process:2537): libfprint-device-DEBUG: 05:03:05.723: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
174s (process:2537): libfprint-device-DEBUG: 05:03:05.723: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s 
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ff8b40e540 (FpiDeviceEgisMoc at 0x1e30be0)>, 10, <FPrint.Print object at 0x3ff8b413680 (FpPrint at 0x1e3b090)>, None, None)
174s enroll new finger done
174s listing - device should have 2 prints
174s deleting first print
174s delete done
174s listing - device should only have second print
174s clear device storage
174s clear done
174s listing - device should be empty
174s ** (umockdev-run:2533): DEBUG: 05:03:05.737: umockdev.vala:154: Removing test bed /tmp/umockdev.86K112
174s (umockdev-run:2533): GLib-DEBUG: 05:03:05.741: unsetenv() is not thread-safe and should not be used after threads are created
174s PASS: libfprint-2/driver-egismoc.test
174s Running test: libfprint-2/driver-egismoc-0586.test
174s ** (umockdev-run:2545): DEBUG: 05:03:05.773: umockdev.vala:127: Created udev test bed /tmp/umockdev.04A312
174s ** (umockdev-run:2545): DEBUG: 05:03:05.774: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-7
174s ** (umockdev-run:2545): DEBUG: 05:03:05.775: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-7 (subsystem usb)
174s ** (umockdev-run:2545): DEBUG: 05:03:05.777: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.04A312/dev/bus/usb/001/021
174s ** (umockdev-run:2545): DEBUG: 05:03:05.777: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
174s ** (umockdev-run:2545): DEBUG: 05:03:05.778: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
174s ** (umockdev-run:2545): DEBUG: 05:03:05.779: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.04A312/dev/bus/usb/001/001
174s ** (umockdev-run:2545): DEBUG: 05:03:05.779: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0
174s ** (umockdev-run:2545): DEBUG: 05:03:05.779: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
174s (process:2549): libfprint-context-DEBUG: 05:03:05.838: Initializing FpContext (libfprint version 1.94.9+tod1)
174s (process:2549): libfprint-tod-DEBUG: 05:03:05.838: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.839: 52588291: ../libfprint/drivers/egismoc/egismoc.c:1597
174s (process:2549): libfprint-context-DEBUG: 05:03:05.839: No driver found for USB device 1D6B:0002
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.839: egismoc_probe enter --> 
174s (process:2549): libfprint-device-DEBUG: 05:03:05.840: Device reported probe completion
174s (process:2549): libfprint-device-DEBUG: 05:03:05.841: Completing action FPI_DEVICE_ACTION_PROBE in idle!
174s (process:2549): libfprint-device-DEBUG: 05:03:05.841: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.841: Opening device
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.842: [egismoc] DEV_INIT_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.842: [egismoc] DEV_INIT_STATES entering state 1
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.842: [egismoc] DEV_INIT_STATES entering state 2
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.843: [egismoc] DEV_INIT_STATES entering state 3
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.843: [egismoc] DEV_INIT_STATES entering state 4
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.843: [egismoc] DEV_INIT_STATES entering state 5
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.843: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.843: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.843: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.844: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.844: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.844: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.844: Firmware version callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.844: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.844: Device firmware version is 9050.6.2.56
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.844: [egismoc] DEV_INIT_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.844: Task SSM done
174s (process:2549): libfprint-device-DEBUG: 05:03:05.844: Device reported open completion
174s (process:2549): libfprint-device-DEBUG: 05:03:05.844: Completing action FPI_DEVICE_ACTION_OPEN in idle!
174s (process:2549): libfprint-device-DEBUG: 05:03:05.844: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.845: List
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.845: [egismoc] LIST_STATES entering state 0
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.845: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.845: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.845: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.845: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.845: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.845: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.845: List callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.845: Device fingerprint 1: FP1-20240417-7-67C37FA4-root
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.845: Number of currently enrolled fingerprints on the device is 1
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.845: [egismoc] LIST_STATES entering state 1
174s (process:2549): libfprint-device-DEBUG: 05:03:05.845: Device reported listing completion
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.845: [egismoc] LIST_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.846: Task SSM done
174s (process:2549): libfprint-device-DEBUG: 05:03:05.846: Completing action FPI_DEVICE_ACTION_LIST in idle!
174s (process:2549): libfprint-device-DEBUG: 05:03:05.846: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.846: Clear storage
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.846: [egismoc] DELETE_STATES entering state 0
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.846: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.846: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.846: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.846: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.846: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.846: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.846: List callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.846: Device fingerprint 1: FP1-20240417-7-67C37FA4-root
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.846: Number of currently enrolled fingerprints on the device is 1
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.846: [egismoc] DELETE_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.846: Get delete command
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.846: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.846: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.846: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.847: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.847: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.847: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.847: Delete callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.847: Response prefix valid: yes
174s (process:2549): libfprint-device-DEBUG: 05:03:05.847: Device reported deletion completion
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.847: [egismoc] DELETE_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.847: Task SSM done
174s (process:2549): libfprint-device-DEBUG: 05:03:05.847: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
174s (process:2549): libfprint-device-DEBUG: 05:03:05.847: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.847: List
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.847: [egismoc] LIST_STATES entering state 0
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.847: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.847: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.847: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.847: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.848: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.848: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.848: List callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.848: Number of currently enrolled fingerprints on the device is 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.848: [egismoc] LIST_STATES entering state 1
174s (process:2549): libfprint-device-DEBUG: 05:03:05.848: Device reported listing completion
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.848: [egismoc] LIST_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.848: Task SSM done
174s (process:2549): libfprint-device-DEBUG: 05:03:05.848: Completing action FPI_DEVICE_ACTION_LIST in idle!
174s (process:2549): libfprint-device-DEBUG: 05:03:05.848: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2549): libfprint-device-DEBUG: 05:03:05.848: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.848: Enroll
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.848: [egismoc] ENROLL_STATES entering state 0
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.848: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.848: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.848: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.848: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.849: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.849: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.849: List callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.849: Number of currently enrolled fingerprints on the device is 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.849: [egismoc] ENROLL_STATES entering state 1
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.849: [egismoc] ENROLL_STATES entering state 2
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.849: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.849: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.849: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.849: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.850: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.850: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.850: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.850: [egismoc] ENROLL_STATES entering state 3
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.850: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.850: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.850: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.850: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.850: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.850: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.850: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.850: [egismoc] ENROLL_STATES entering state 4
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.850: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.850: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.851: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.851: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.851: [egismoc] ENROLL_STATES entering state 5
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.851: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.851: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.851: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.851: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.852: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.852: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.852: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.852: [egismoc] ENROLL_STATES entering state 6
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.852: Get check command
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.852: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.852: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.852: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.852: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.852: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.852: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.852: Enroll check callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.852: Response suffix valid: yes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.852: [egismoc] ENROLL_STATES entering state 7
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.852: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.852: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.852: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.853: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.853: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.853: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.853: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.853: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.853: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.853: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.853: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.853: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.853: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.853: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.853: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.853: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.853: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.853: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.853: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.854: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.854: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.854: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.854: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.854: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.854: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.854: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.854: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.854: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.854: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.854: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.855: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.855: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.855: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.855: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.855: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.855: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.855: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.855: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.855: Partial capture successful. Please touch the sensor again (1/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.855: Device reported enroll progress, reported 1 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.855: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.855: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.855: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.855: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.856: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.856: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.856: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.856: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.856: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.856: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.856: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.856: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.856: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.857: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.857: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.857: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.857: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.857: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.857: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.857: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.857: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.857: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.857: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.857: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.857: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.857: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.858: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.858: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.858: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.858: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.858: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.858: Partial capture successful. Please touch the sensor again (2/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.858: Device reported enroll progress, reported 2 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.858: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.858: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.858: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.858: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.858: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.858: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.858: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.858: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.858: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.858: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.858: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.858: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.859: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.859: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.859: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.859: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.859: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.859: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.859: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.859: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.859: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.859: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.859: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.859: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.859: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.860: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.860: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.860: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.860: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.860: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.860: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.860: Partial capture successful. Please touch the sensor again (3/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.860: Device reported enroll progress, reported 3 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.860: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.860: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.860: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.860: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.861: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.861: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.861: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.861: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.861: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.861: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.861: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.861: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.861: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.862: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.862: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.862: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.862: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.862: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.862: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.862: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.862: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.862: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.862: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.862: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.862: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.862: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.863: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.863: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.863: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.863: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.863: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.863: Partial capture successful. Please touch the sensor again (4/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.863: Device reported enroll progress, reported 4 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.863: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.863: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.863: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.863: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.863: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.863: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.863: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.863: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.863: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.863: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.863: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.863: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.864: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.864: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.864: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.864: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.864: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.864: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.864: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.864: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.864: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.864: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.864: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.864: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.864: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.865: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.865: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.865: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.865: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.865: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.865: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.865: Partial capture successful. Please touch the sensor again (5/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.865: Device reported enroll progress, reported 5 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.865: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.865: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.865: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.865: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.865: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.866: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.866: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.866: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.866: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.866: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.866: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.866: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.866: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.866: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.866: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.866: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.866: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.866: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.866: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.867: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.867: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.867: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.867: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.867: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.867: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.867: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.867: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.867: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.867: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.867: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.867: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.867: Partial capture successful. Please touch the sensor again (6/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.867: Device reported enroll progress, reported 6 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.867: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.867: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.867: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.867: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.868: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.868: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.868: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.868: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.868: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.868: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.868: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.868: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.868: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.869: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.869: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.869: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.869: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.869: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.869: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.869: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.869: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.869: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.869: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.869: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.869: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.870: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.870: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.870: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.870: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.870: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.870: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.870: Partial capture successful. Please touch the sensor again (7/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.870: Device reported enroll progress, reported 7 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.870: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.870: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.870: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.870: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.870: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.871: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.871: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.871: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.871: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.871: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.871: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.871: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.871: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.871: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.871: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.871: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.871: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.871: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.871: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.872: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.872: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.872: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.872: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.872: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.872: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.872: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.872: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.872: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.872: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.872: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.872: Response suffix valid: NO
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.872: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.872: Response suffix valid: yes
174s (process:2549): libfprint-device-DEBUG: 05:03:05.872: Device reported enroll progress, reported 7 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.872: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.872: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.872: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.872: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.873: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.873: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.873: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.873: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.873: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.873: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.873: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.873: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.873: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.874: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.874: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.874: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.874: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.874: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.874: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.874: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.874: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.874: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.874: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.874: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.874: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.874: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.874: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.874: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.874: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.874: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.874: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.874: Partial capture successful. Please touch the sensor again (8/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.874: Device reported enroll progress, reported 8 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.874: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.874: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.874: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.874: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.875: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.875: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.875: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.875: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.875: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.875: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.875: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.875: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.875: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.876: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.876: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.876: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.876: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.876: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.876: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.876: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.876: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.876: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.876: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.876: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.876: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.876: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.876: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.876: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.876: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.876: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.876: Response suffix valid: NO
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.876: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.876: Response suffix valid: yes
174s (process:2549): libfprint-device-DEBUG: 05:03:05.876: Device reported enroll progress, reported 8 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.876: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.876: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.876: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.876: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.877: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.877: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.877: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.877: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.877: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.877: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.877: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.877: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.877: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.877: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.877: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.877: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.877: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.877: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.877: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.878: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.878: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.878: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.878: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.878: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.878: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.878: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.878: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.878: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.878: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.878: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.878: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.878: Partial capture successful. Please touch the sensor again (9/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.878: Device reported enroll progress, reported 9 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.878: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.878: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.878: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.878: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.879: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.879: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.879: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.879: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.879: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.879: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.879: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.879: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.879: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.880: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.880: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.880: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.880: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.880: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.880: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.880: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.880: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.880: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.880: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.880: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.880: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.880: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.880: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.880: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.880: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.880: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.880: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.880: Partial capture successful. Please touch the sensor again (10/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.880: Device reported enroll progress, reported 10 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.880: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.880: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.880: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.880: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.881: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.881: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.881: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.881: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.881: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.881: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.881: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.881: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.881: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.882: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.882: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.882: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.882: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.882: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.882: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.882: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.882: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.882: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.882: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.882: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.882: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.882: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.882: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.882: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.882: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.882: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.882: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.882: Partial capture successful. Please touch the sensor again (11/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.882: Device reported enroll progress, reported 11 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.882: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.882: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.882: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.882: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.883: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.883: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.883: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.883: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.883: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.883: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.883: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.883: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.883: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.884: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.884: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.884: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.884: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.884: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.884: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.884: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.884: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.884: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.884: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.884: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.884: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.884: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.884: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.884: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.884: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.884: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.884: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.884: Partial capture successful. Please touch the sensor again (12/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.884: Device reported enroll progress, reported 12 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.884: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.884: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.884: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.884: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.885: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.885: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.885: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.885: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.885: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.885: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.885: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.885: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.885: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.886: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.886: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.886: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.886: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.886: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.886: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.886: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.886: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.886: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.886: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.886: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.886: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.886: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.887: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.887: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.887: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.887: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.887: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.887: Partial capture successful. Please touch the sensor again (13/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.887: Device reported enroll progress, reported 13 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.887: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.887: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.887: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.887: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.887: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.887: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.887: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.887: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.887: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.887: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.887: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.887: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.888: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.888: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.888: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.888: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.888: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.888: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.888: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.888: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.888: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.888: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.888: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.888: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.888: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.889: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.889: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.889: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.889: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.889: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.889: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.889: Partial capture successful. Please touch the sensor again (14/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.889: Device reported enroll progress, reported 14 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.889: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.889: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.889: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.889: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.889: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.890: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.890: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.890: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.890: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.890: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.890: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.890: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.890: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.890: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.890: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.890: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.890: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.890: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.890: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.891: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.891: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.891: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.891: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.891: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.891: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.891: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.891: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.891: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.891: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.891: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.891: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.891: Partial capture successful. Please touch the sensor again (15/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.891: Device reported enroll progress, reported 15 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.891: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.891: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.891: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.891: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.891: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.892: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.892: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.892: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.892: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.892: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.892: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.892: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.892: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.892: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.892: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.892: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.892: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.892: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.892: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.893: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.893: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.893: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.893: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.893: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.893: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.893: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.893: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.893: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.893: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.893: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.893: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.893: Partial capture successful. Please touch the sensor again (16/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.893: Device reported enroll progress, reported 16 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.893: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.893: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.893: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.893: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.894: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.894: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.894: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.894: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.894: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.894: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.894: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.894: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.894: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.895: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.895: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.895: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.895: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.895: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.895: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.895: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.895: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.895: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.895: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.895: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.895: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.895: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.896: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.896: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.896: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.896: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.896: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.896: Partial capture successful. Please touch the sensor again (17/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.896: Device reported enroll progress, reported 17 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.896: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.896: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.896: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.896: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.896: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.896: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.896: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.896: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.896: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.896: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.896: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.896: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.897: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.897: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.897: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.897: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.897: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.897: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.897: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.897: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.897: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.897: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.897: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.897: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.897: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.898: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.898: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.898: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.898: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.898: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.898: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.898: Partial capture successful. Please touch the sensor again (18/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.898: Device reported enroll progress, reported 18 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.898: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.898: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.898: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.898: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.898: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.898: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.898: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.898: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.898: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.899: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.899: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.899: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.899: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.899: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.899: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.899: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.899: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.899: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.899: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.899: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.899: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.899: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.899: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.899: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.899: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.900: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.900: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.900: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.900: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.900: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.900: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.900: Partial capture successful. Please touch the sensor again (19/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.900: Device reported enroll progress, reported 19 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.900: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.900: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.900: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.900: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.900: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.901: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.901: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.901: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.901: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.901: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.901: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.901: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.901: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.902: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.902: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.902: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.902: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.902: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.902: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.902: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.902: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.902: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.902: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.902: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.902: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.902: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.903: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.903: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.903: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.903: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.903: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.903: Partial capture successful. Please touch the sensor again (20/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.903: Device reported enroll progress, reported 20 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.903: [egismoc] ENROLL_STATES entering state 12
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.903: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.903: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.903: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.903: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.904: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.904: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.904: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.904: [egismoc] ENROLL_STATES entering state 13
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.904: New fingerprint ID: FP1-00000000-2-00000000-nobody
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.904: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.904: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.904: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.904: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.904: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.904: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.904: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.904: [egismoc] ENROLL_STATES entering state 14
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.904: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.904: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.904: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.905: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.905: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.905: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.905: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.905: [egismoc] ENROLL_STATES entering state 15
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.905: Enrollment was successful!
174s (process:2549): libfprint-device-DEBUG: 05:03:05.905: Device reported enroll completion
174s (process:2549): libfprint-device-DEBUG: 05:03:05.905: Device reported finger status change: FP_FINGER_STATUS_NONE
174s (process:2549): libfprint-device-DEBUG: 05:03:05.905: Print for finger FP_FINGER_LEFT_INDEX enrolled
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.905: [egismoc] ENROLL_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.905: Task SSM done
174s (process:2549): libfprint-device-DEBUG: 05:03:05.905: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
174s (process:2549): libfprint-device-DEBUG: 05:03:05.905: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.905: List
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.905: [egismoc] LIST_STATES entering state 0
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.905: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.905: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.905: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.905: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.906: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.906: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.906: List callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.906: Device fingerprint 1: FP1-00000000-2-00000000-nobody
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.906: Number of currently enrolled fingerprints on the device is 1
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.906: [egismoc] LIST_STATES entering state 1
174s (process:2549): libfprint-device-DEBUG: 05:03:05.906: Device reported listing completion
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.906: [egismoc] LIST_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.906: Task SSM done
174s (process:2549): libfprint-device-DEBUG: 05:03:05.906: Completing action FPI_DEVICE_ACTION_LIST in idle!
174s (process:2549): libfprint-device-DEBUG: 05:03:05.906: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2549): libfprint-device-DEBUG: 05:03:05.906: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.906: Identify or Verify
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.906: [egismoc] IDENTIFY_STATES entering state 0
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.906: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.906: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.906: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.906: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.906: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.906: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.907: List callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.907: Device fingerprint 1: FP1-00000000-2-00000000-nobody
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.907: Number of currently enrolled fingerprints on the device is 1
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.907: [egismoc] IDENTIFY_STATES entering state 1
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.907: [egismoc] IDENTIFY_STATES entering state 2
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.907: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.907: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.907: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.907: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.907: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.907: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.907: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.907: [egismoc] IDENTIFY_STATES entering state 3
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.907: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.907: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.907: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.907: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.908: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.908: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.908: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.908: [egismoc] IDENTIFY_STATES entering state 4
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.908: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.908: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.908: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.908: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.908: [egismoc] IDENTIFY_STATES entering state 5
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.908: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.908: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.908: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.908: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.908: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.908: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.908: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.908: [egismoc] IDENTIFY_STATES entering state 6
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.908: Get check command
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.908: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.908: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.908: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.909: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.909: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.909: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.909: Identify check callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.909: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.909: Identify successful for: FP1-00000000-2-00000000-nobody
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.909: Verifying against: FP1-00000000-2-00000000-nobody
174s (process:2549): libfprint-device-DEBUG: 05:03:05.909: Device reported verify result
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.909: [egismoc] IDENTIFY_STATES entering state 7
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.909: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.909: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.909: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.909: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.910: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.910: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.910: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.910: [egismoc] IDENTIFY_STATES entering state 8
174s (process:2549): libfprint-device-DEBUG: 05:03:05.910: Device reported verify completion
174s (process:2549): libfprint-device-DEBUG: 05:03:05.910: Device reported finger status change: FP_FINGER_STATUS_NONE
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.910: [egismoc] IDENTIFY_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.910: Task SSM done
174s (process:2549): libfprint-device-DEBUG: 05:03:05.910: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
174s (process:2549): libfprint-device-DEBUG: 05:03:05.910: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2549): libfprint-device-DEBUG: 05:03:05.910: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.910: Identify or Verify
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.910: [egismoc] IDENTIFY_STATES entering state 0
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.910: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.910: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.910: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.910: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.911: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.911: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.911: List callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.911: Device fingerprint 1: FP1-00000000-2-00000000-nobody
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.911: Number of currently enrolled fingerprints on the device is 1
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.911: [egismoc] IDENTIFY_STATES entering state 1
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.911: [egismoc] IDENTIFY_STATES entering state 2
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.911: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.911: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.911: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.911: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.912: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.912: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.912: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.912: [egismoc] IDENTIFY_STATES entering state 3
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.912: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.912: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.912: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.912: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.912: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.912: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.912: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.912: [egismoc] IDENTIFY_STATES entering state 4
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.912: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.912: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.913: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.913: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.913: [egismoc] IDENTIFY_STATES entering state 5
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.913: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.913: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.913: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.913: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.913: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.913: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.913: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.913: [egismoc] IDENTIFY_STATES entering state 6
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.913: Get check command
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.913: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.913: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.913: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.914: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.914: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.914: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.914: Identify check callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.914: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.914: Identify successful for: FP1-00000000-2-00000000-nobody
174s (process:2549): libfprint-device-DEBUG: 05:03:05.914: Device reported identify result
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.914: [egismoc] IDENTIFY_STATES entering state 7
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.914: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.914: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.914: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.914: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.914: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.915: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.915: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.915: [egismoc] IDENTIFY_STATES entering state 8
174s (process:2549): libfprint-device-DEBUG: 05:03:05.915: Device reported identify completion
174s (process:2549): libfprint-device-DEBUG: 05:03:05.915: Device reported finger status change: FP_FINGER_STATUS_NONE
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.915: [egismoc] IDENTIFY_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.915: Task SSM done
174s (process:2549): libfprint-device-DEBUG: 05:03:05.915: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
174s (process:2549): libfprint-device-DEBUG: 05:03:05.915: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2549): libfprint-device-DEBUG: 05:03:05.915: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.915: Enroll
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.915: [egismoc] ENROLL_STATES entering state 0
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.915: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.915: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.915: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.915: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.916: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.916: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.916: List callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.916: Device fingerprint 1: FP1-00000000-2-00000000-nobody
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.916: Number of currently enrolled fingerprints on the device is 1
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.916: [egismoc] ENROLL_STATES entering state 1
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.916: [egismoc] ENROLL_STATES entering state 2
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.916: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.916: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.916: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.916: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.916: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.916: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.916: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.916: [egismoc] ENROLL_STATES entering state 3
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.916: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.917: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.917: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.917: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.917: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.917: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.917: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.917: [egismoc] ENROLL_STATES entering state 4
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.917: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.917: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.917: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.917: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.917: [egismoc] ENROLL_STATES entering state 5
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.917: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.917: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.917: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.918: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.918: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.918: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.918: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.918: [egismoc] ENROLL_STATES entering state 6
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.918: Get check command
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.918: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.918: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.918: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.918: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.918: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.918: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.918: Enroll check callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.918: Response suffix valid: NO
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.918: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.918: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.918: Task SSM done
174s (process:2549): libfprint-device-DEBUG: 05:03:05.918: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL
174s (process:2549): libfprint-device-DEBUG: 05:03:05.918: Device reported enroll completion
174s (process:2549): libfprint-device-DEBUG: 05:03:05.918: Device reported finger status change: FP_FINGER_STATUS_NONE
174s (process:2549): libfprint-device-DEBUG: 05:03:05.918: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
174s (process:2549): libfprint-device-DEBUG: 05:03:05.918: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.919: List
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.919: [egismoc] LIST_STATES entering state 0
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.919: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.919: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.919: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.919: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.919: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.919: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.919: List callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.919: Device fingerprint 1: FP1-00000000-2-00000000-nobody
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.919: Number of currently enrolled fingerprints on the device is 1
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.919: [egismoc] LIST_STATES entering state 1
174s (process:2549): libfprint-device-DEBUG: 05:03:05.919: Device reported listing completion
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.919: [egismoc] LIST_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.919: Task SSM done
174s (process:2549): libfprint-device-DEBUG: 05:03:05.919: Completing action FPI_DEVICE_ACTION_LIST in idle!
174s (process:2549): libfprint-device-DEBUG: 05:03:05.919: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2549): libfprint-device-DEBUG: 05:03:05.919: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.919: Enroll
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.919: [egismoc] ENROLL_STATES entering state 0
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.919: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.919: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.919: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.919: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.920: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.920: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.920: List callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.920: Device fingerprint 1: FP1-00000000-2-00000000-nobody
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.920: Number of currently enrolled fingerprints on the device is 1
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.920: [egismoc] ENROLL_STATES entering state 1
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.920: [egismoc] ENROLL_STATES entering state 2
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.920: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.920: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.920: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.920: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.921: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.921: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.921: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.921: [egismoc] ENROLL_STATES entering state 3
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.921: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.921: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.921: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.921: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.921: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.921: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.921: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.921: [egismoc] ENROLL_STATES entering state 4
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.921: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.921: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.922: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.922: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.922: [egismoc] ENROLL_STATES entering state 5
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.922: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.922: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.922: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.922: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.922: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.922: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.922: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.922: [egismoc] ENROLL_STATES entering state 6
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.922: Get check command
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.922: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.922: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.922: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.922: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.923: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.923: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.923: Enroll check callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.923: Response suffix valid: yes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.923: [egismoc] ENROLL_STATES entering state 7
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.923: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.923: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.923: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.923: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.923: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.923: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.923: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.923: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.923: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.923: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.923: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.924: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.924: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.924: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.924: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.924: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.924: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.924: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.924: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.924: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.925: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.925: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.925: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.925: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.925: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.925: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.925: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.925: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.925: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.925: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.925: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.925: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.925: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.925: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.925: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.925: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.925: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.925: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.925: Partial capture successful. Please touch the sensor again (1/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.925: Device reported enroll progress, reported 1 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.926: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.926: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.926: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.926: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.926: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.926: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.926: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.926: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.926: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.926: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.926: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.926: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.926: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.927: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.927: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.927: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.927: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.927: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.927: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.927: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.927: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.927: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.927: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.927: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.927: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.927: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.928: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.928: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.928: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.928: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.928: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.928: Partial capture successful. Please touch the sensor again (2/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.928: Device reported enroll progress, reported 2 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.928: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.928: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.928: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.928: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.928: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.928: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.928: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.928: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.928: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.928: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.928: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.928: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.929: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.929: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.929: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.929: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.929: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.929: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.929: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.929: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.929: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.929: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.929: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.929: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.930: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.930: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.930: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.930: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.930: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.930: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.930: Partial capture successful. Please touch the sensor again (3/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.930: Device reported enroll progress, reported 3 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.930: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.930: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.930: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.930: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.930: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.931: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.931: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.931: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.931: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.931: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.931: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.931: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.931: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.932: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.932: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.932: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.932: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.932: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.932: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.932: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.932: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.932: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.932: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.932: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.932: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.932: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.933: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.933: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.933: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.933: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.933: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.933: Partial capture successful. Please touch the sensor again (4/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.933: Device reported enroll progress, reported 4 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.933: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.933: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.933: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.933: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.933: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.933: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.933: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.933: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.933: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.933: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.933: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.933: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.934: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.934: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.934: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.934: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.934: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.934: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.934: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.934: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.934: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.934: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.934: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.934: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.934: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.935: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.935: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.935: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.935: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.935: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.935: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.935: Partial capture successful. Please touch the sensor again (5/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.935: Device reported enroll progress, reported 5 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.935: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.935: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.935: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.935: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.935: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.935: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.935: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.935: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.935: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.935: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.935: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.935: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.936: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.936: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.936: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.936: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.936: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.936: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.936: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.936: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.936: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.936: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.936: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.936: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.936: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.937: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.937: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.937: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.937: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.937: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.937: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.937: Partial capture successful. Please touch the sensor again (6/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.937: Device reported enroll progress, reported 6 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.937: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.937: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.937: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.937: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.937: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.938: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.938: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.938: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.938: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.938: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.938: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.938: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.938: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.938: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.938: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.938: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.938: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.938: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.938: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.938: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.938: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.938: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.938: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.938: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.938: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.939: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.939: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.939: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.939: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.939: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.939: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.939: Partial capture successful. Please touch the sensor again (7/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.939: Device reported enroll progress, reported 7 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.939: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.939: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.939: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.939: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.939: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.939: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.940: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.940: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.940: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.940: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.940: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.940: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.940: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.940: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.940: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.940: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.940: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.940: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.940: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.940: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.940: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.940: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.940: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.940: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.940: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.941: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.941: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.941: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.941: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.941: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.941: Response suffix valid: NO
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.941: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.941: Response suffix valid: yes
174s (process:2549): libfprint-device-DEBUG: 05:03:05.941: Device reported enroll progress, reported 7 of 20 have been completed
174s listing - device should have prints
174s clear device storage
174s clear done
174s listing - device should be empty
174s enrolling
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 1, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 2, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 3, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 4, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 5, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 6, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 7, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 8, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 9, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 10, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 11, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 12, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 13, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 14, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 15, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 16, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 17, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 18, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 19, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 20, <FPrint.Print object at 0x3ffb050fcc0 (FpPrint at 0x1d46b80)>, None, None)
174s enroll done
174s listing - device should have 1 print
174s verifying
174s verify done
174s async identifying
174s indentification_done:  <FPrint.Print object at 0x3ffb0513540 (FpPrint at 0x1d53d40)> <FPrint.Print object at 0x3ffb0513580 (FpPrint at 0x1d57950)>
174s try to enroll duplicate
174s duplicate enroll attempt done
174s listing - device should still only have 1 print
174s enroll new finger
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 1, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 2, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 3, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 4, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 5, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 6, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
174s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 7, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
174s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>(process:2549): libfprint-SSM-DEBUG: 05:03:05.941: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.941: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.941: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.941: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.941: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.942: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.942: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.942: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.942: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.942: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.942: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.942: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.942: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.942: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.942: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.942: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.942: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.942: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.942: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.942: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.942: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.942: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.942: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.942: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.942: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.943: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.943: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.943: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.943: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.943: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.943: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.943: Partial capture successful. Please touch the sensor again (8/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.943: Device reported enroll progress, reported 8 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.943: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.943: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.943: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.943: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.943: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.944: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.944: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.944: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.944: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.944: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.944: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.944: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.944: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.944: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.944: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.944: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.944: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.944: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.944: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.944: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.944: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.944: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.944: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.944: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.944: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.945: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.945: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.945: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.945: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.945: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.945: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.945: Partial capture successful. Please touch the sensor again (9/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.945: Device reported enroll progress, reported 9 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.945: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.945: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.945: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.945: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.945: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.945: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.945: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.945: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.945: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.945: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.945: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.945: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.946: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.946: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.946: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.946: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.946: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.946: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.946: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.946: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.946: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.946: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.946: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.946: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.946: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.947: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.947: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.947: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.947: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.947: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.947: Response suffix valid: NO
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.947: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.947: Response suffix valid: yes
174s (process:2549): libfprint-device-DEBUG: 05:03:05.947: Device reported enroll progress, reported 9 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.947: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.947: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.947: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.947: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.947: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.948: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.948: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.948: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.948: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.948: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.948: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.948: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.948: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.948: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.948: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.948: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.948: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.948: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.948: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.948: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.948: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.948: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.948: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.948: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.948: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.949: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.949: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.949: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.949: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.949: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.949: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.949: Partial capture successful. Please touch the sensor again (10/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.949: Device reported enroll progress, reported 10 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.949: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.949: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.949: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.949: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.949: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.949: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.949: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.949: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.949: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.949: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.949: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.949: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.950: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.950: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.950: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.950: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.950: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.950: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.950: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.950: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.950: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.950: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.950: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.950: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.950: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.951: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.951: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.951: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.951: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.951: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.951: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.951: Partial capture successful. Please touch the sensor again (11/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.951: Device reported enroll progress, reported 11 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.951: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.951: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.951: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.951: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.951: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.952: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.952: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.952: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.952: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.952: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.952: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.952: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.952: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.952: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.952: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.952: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.952: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.952: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.952: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.953: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.953: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.953: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.953: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.953: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.953: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.953: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.953: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.953: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.953: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.953: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.953: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.953: Partial capture successful. Please touch the sensor again (12/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.953: Device reported enroll progress, reported 12 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.953: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.953: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.953: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.953: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.954: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.954: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.954: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.954: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.954: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.954: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.954: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.954: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.954: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.955: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.955: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.955: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.955: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.955: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.955: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.955: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.955: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.955: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.955: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.955: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.955: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.955: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.956: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.956: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.956: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.956: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.956: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.956: Partial capture successful. Please touch the sensor again (13/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.956: Device reported enroll progress, reported 13 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.956: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.956: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.956: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.956: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.956: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.957: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.957: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.957: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.957: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.957: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.957: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.957: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.957: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.957: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.957: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.957: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.957: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.957: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.957: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.958: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.958: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.958: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.958: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.958: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.958: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.958: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.958: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.958: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.958: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.958: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.958: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.958: Partial capture successful. Please touch the sensor again (14/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.958: Device reported enroll progress, reported 14 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.958: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.958: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.958: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.958: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.959: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.959: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.959: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.959: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.959: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.959: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.959: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.959: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.959: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.960: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.960: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.960: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.960: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.960: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.960: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.960: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.960: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.960: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.960: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.960: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.960: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.961: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.961: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.961: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.961: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.961: Response prefix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.961: Response suffix valid: yes
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.961: Partial capture successful. Please touch the sensor again (15/20)
174s (process:2549): libfprint-device-DEBUG: 05:03:05.961: Device reported enroll progress, reported 15 of 20 have been completed
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.961: [egismoc] ENROLL_STATES entering state 8
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.961: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.961: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.961: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.961: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.962: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.962: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.962: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.962: [egismoc] ENROLL_STATES entering state 9
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.962: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.962: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.962: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.962: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.962: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.962: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.962: Task SSM next state callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.962: [egismoc] ENROLL_STATES entering state 10
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.962: Wait for finger on sensor
174s (process:2549): libfprint-device-DEBUG: 05:03:05.962: Device reported finger status change: FP_FINGER_STATUS_NEEDED
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.963: Finger on sensor callback
174s (process:2549): libfprint-device-DEBUG: 05:03:05.963: Device reported finger status change: FP_FINGER_STATUS_PRESENT
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.963: [egismoc] ENROLL_STATES entering state 11
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.963: Execute command and get response
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.963: Get check bytes
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.963: [egismoc] CMD_STATES entering state 0
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.963: [egismoc] CMD_STATES entering state 1
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.963: Command receive callback
174s (process:2549): libfprint-SSM-DEBUG: 05:03:05.963: [egismoc] CMD_STATES completed successfully
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.963: Read capture callback
174s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.963: Response prefix valid: yes
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.963: Response suffix valid: yes
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.963: Partial capture successful. Please touch the sensor again (16/20)
175s (process:2549): libfprint-device-DEBUG: 05:03:05.963: Device reported enroll progress, reported 16 of 20 have been completed
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.963: [egismoc] ENROLL_STATES entering state 8
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.963: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.963: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.963: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.964: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.964: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.964: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.964: Task SSM next state callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.964: [egismoc] ENROLL_STATES entering state 9
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.964: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.964: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.964: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.964: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.965: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.965: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.965: Task SSM next state callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.965: [egismoc] ENROLL_STATES entering state 10
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.965: Wait for finger on sensor
175s (process:2549): libfprint-device-DEBUG: 05:03:05.965: Device reported finger status change: FP_FINGER_STATUS_NEEDED
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.965: Finger on sensor callback
175s (process:2549): libfprint-device-DEBUG: 05:03:05.965: Device reported finger status change: FP_FINGER_STATUS_PRESENT
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.965: [egismoc] ENROLL_STATES entering state 11
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.965: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.965: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.965: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.965: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.965: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.965: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.965: Read capture callback
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.965: Response prefix valid: yes
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.965: Response suffix valid: yes
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.965: Partial capture successful. Please touch the sensor again (17/20)
175s (process:2549): libfprint-device-DEBUG: 05:03:05.965: Device reported enroll progress, reported 17 of 20 have been completed
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.966: [egismoc] ENROLL_STATES entering state 8
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.966: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.966: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.966: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.966: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.966: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.966: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.966: Task SSM next state callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.966: [egismoc] ENROLL_STATES entering state 9
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.966: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.966: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.966: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.966: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.967: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.967: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.967: Task SSM next state callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.967: [egismoc] ENROLL_STATES entering state 10
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.967: Wait for finger on sensor
175s (process:2549): libfprint-device-DEBUG: 05:03:05.967: Device reported finger status change: FP_FINGER_STATUS_NEEDED
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.967: Finger on sensor callback
175s (process:2549): libfprint-device-DEBUG: 05:03:05.967: Device reported finger status change: FP_FINGER_STATUS_PRESENT
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.967: [egismoc] ENROLL_STATES entering state 11
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.967: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.967: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.967: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.968: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.968: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.968: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.968: Read capture callback
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.968: Response prefix valid: yes
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.968: Response suffix valid: yes
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.968: Partial capture successful. Please touch the sensor again (18/20)
175s (process:2549): libfprint-device-DEBUG: 05:03:05.968: Device reported enroll progress, reported 18 of 20 have been completed
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.968: [egismoc] ENROLL_STATES entering state 8
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.968: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.968: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.968: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.968: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.968: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.969: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.969: Task SSM next state callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.969: [egismoc] ENROLL_STATES entering state 9
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.969: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.969: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.969: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.969: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.969: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.969: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.969: Task SSM next state callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.969: [egismoc] ENROLL_STATES entering state 10
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.969: Wait for finger on sensor
175s (process:2549): libfprint-device-DEBUG: 05:03:05.969: Device reported finger status change: FP_FINGER_STATUS_NEEDED
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.969: Finger on sensor callback
175s (process:2549): libfprint-device-DEBUG: 05:03:05.969: Device reported finger status change: FP_FINGER_STATUS_PRESENT
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.969: [egismoc] ENROLL_STATES entering state 11
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.969: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.969: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.969: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.970: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.970: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.970: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.970: Read capture callback
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.970: Response prefix valid: yes
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.970: Response suffix valid: yes
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.970: Partial capture successful. Please touch the sensor again (19/20)
175s (process:2549): libfprint-device-DEBUG: 05:03:05.970: Device reported enroll progress, reported 19 of 20 have been completed
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.970: [egismoc] ENROLL_STATES entering state 8
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.970: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.970: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.970: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.970: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.971: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.971: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.971: Task SSM next state callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.971: [egismoc] ENROLL_STATES entering state 9
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.971: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.971: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.971: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.971: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.971: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.972: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.972: Task SSM next state callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.972: [egismoc] ENROLL_STATES entering state 10
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.972: Wait for finger on sensor
175s (process:2549): libfprint-device-DEBUG: 05:03:05.972: Device reported finger status change: FP_FINGER_STATUS_NEEDED
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.972: Finger on sensor callback
175s (process:2549): libfprint-device-DEBUG: 05:03:05.972: Device reported finger status change: FP_FINGER_STATUS_PRESENT
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.972: [egismoc] ENROLL_STATES entering state 11
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.972: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.972: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.972: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.972: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.972: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.972: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.972: Read capture callback
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.972: Response prefix valid: yes
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.972: Response suffix valid: yes
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.972: Partial capture successful. Please touch the sensor again (20/20)
175s (process:2549): libfprint-device-DEBUG: 05:03:05.972: Device reported enroll progress, reported 20 of 20 have been completed
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.972: [egismoc] ENROLL_STATES entering state 12
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.972: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.972: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.972: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.973: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.973: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.973: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.973: Task SSM next state callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.973: [egismoc] ENROLL_STATES entering state 13
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.973: New fingerprint ID: FP1-00000000-7-00000000-nobody
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.973: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.973: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.973: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.974: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.974: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.974: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.974: Task SSM next state callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.974: [egismoc] ENROLL_STATES entering state 14
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.974: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.974: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.974: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.974: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.974: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.974: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.974: Task SSM next state callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.974: [egismoc] ENROLL_STATES entering state 15
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.974: Enrollment was successful!
175s (process:2549): libfprint-device-DEBUG: 05:03:05.974: Device reported enroll completion
175s (process:2549): libfprint-device-DEBUG: 05:03:05.974: Device reported finger status change: FP_FINGER_STATUS_NONE
175s (process:2549): libfprint-device-DEBUG: 05:03:05.974: Print for finger FP_FINGER_RIGHT_INDEX enrolled
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.974: [egismoc] ENROLL_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.974: Task SSM done
175s (process:2549): libfprint-device-DEBUG: 05:03:05.974: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
175s (process:2549): libfprint-device-DEBUG: 05:03:05.974: Updated temperature model after 0.06 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.975: List
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.975: [egismoc] LIST_STATES entering state 0
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.975: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.975: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.975: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.975: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.975: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.975: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.975: List callback
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.975: Device fingerprint 1: FP1-00000000-2-00000000-nobody
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.975: Device fingerprint 2: FP1-00000000-7-00000000-nobody
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.975: Number of currently enrolled fingerprints on the device is 2
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.975: [egismoc] LIST_STATES entering state 1
175s (process:2549): libfprint-device-DEBUG: 05:03:05.975: Device reported listing completion
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.975: [egismoc] LIST_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.975: Task SSM done
175s (process:2549): libfprint-device-DEBUG: 05:03:05.975: Completing action FPI_DEVICE_ACTION_LIST in idle!
175s (process:2549): libfprint-device-DEBUG: 05:03:05.975: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.975: Delete
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.975: [egismoc] DELETE_STATES entering state 0
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.975: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.975: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.975: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.976: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.976: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.976: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.976: List callback
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.976: Device fingerprint 1: FP1-00000000-2-00000000-nobody
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.976: Device fingerprint 2: FP1-00000000-7-00000000-nobody
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.976: Number of currently enrolled fingerprints on the device is 2
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.976: [egismoc] DELETE_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.976: Get delete command
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.976: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody)
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.976: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.976: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.976: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.976: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.977: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.977: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.977: Delete callback
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.977: Response prefix valid: yes
175s (process:2549): libfprint-device-DEBUG: 05:03:05.977: Device reported deletion completion
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.977: [egismoc] DELETE_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.977: Task SSM done
175s (process:2549): libfprint-device-DEBUG: 05:03:05.977: Completing action FPI_DEVICE_ACTION_DELETE in idle!
175s (process:2549): libfprint-device-DEBUG: 05:03:05.977: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.977: List
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.977: [egismoc] LIST_STATES entering state 0
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.977: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.977: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.977: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.977: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.977: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.977: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.977: List callback
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.977: Device fingerprint 1: FP1-00000000-7-00000000-nobody
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.978: Number of currently enrolled fingerprints on the device is 1
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.978: [egismoc] LIST_STATES entering state 1
175s (process:2549): libfprint-device-DEBUG: 05:03:05.978: Device reported listing completion
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.978: [egismoc] LIST_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.978: Task SSM done
175s (process:2549): libfprint-device-DEBUG: 05:03:05.978: Completing action FPI_DEVICE_ACTION_LIST in idle!
175s (process:2549): libfprint-device-DEBUG: 05:03:05.978: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.978: Clear storage
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.978: [egismoc] DELETE_STATES entering state 0
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.978: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.978: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.978: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.978: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.978: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.978: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.978: List callback
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.978: Device fingerprint 1: FP1-00000000-7-00000000-nobody
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.978: Number of currently enrolled fingerprints on the device is 1
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.978: [egismoc] DELETE_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.978: Get delete command
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.978: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.978: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.978: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.978: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.979: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.979: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.979: Delete callback
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.979: Response prefix valid: yes
175s (process:2549): libfprint-device-DEBUG: 05:03:05.979: Device reported deletion completion
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.979: [egismoc] DELETE_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.979: Task SSM done
175s (process:2549): libfprint-device-DEBUG: 05:03:05.979: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
175s (process:2549): libfprint-device-DEBUG: 05:03:05.979: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.979: List
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.979: [egismoc] LIST_STATES entering state 0
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.979: Execute command and get response
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.979: Get check bytes
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.979: [egismoc] CMD_STATES entering state 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.979: [egismoc] CMD_STATES entering state 1
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.979: Command receive callback
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.980: [egismoc] CMD_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.980: List callback
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.980: Number of currently enrolled fingerprints on the device is 0
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.980: [egismoc] LIST_STATES entering state 1
175s (process:2549): libfprint-device-DEBUG: 05:03:05.980: Device reported listing completion
175s (process:2549): libfprint-SSM-DEBUG: 05:03:05.980: [egismoc] LIST_STATES completed successfully
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.980: Task SSM done
175s (process:2549): libfprint-device-DEBUG: 05:03:05.980: Completing action FPI_DEVICE_ACTION_LIST in idle!
175s (process:2549): libfprint-device-DEBUG: 05:03:05.980: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.980: Closing device
175s (process:2549): libfprint-egismoc-DEBUG: 05:03:05.980: Cancel
175s (process:2549): libfprint-device-DEBUG: 05:03:05.980: Device reported close completion
175s (process:2549): libfprint-device-DEBUG: 05:03:05.980: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
175s (process:2549): libfprint-device-DEBUG: 05:03:05.980: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
175s 
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
175s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 8, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
175s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 9, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
175s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
175s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 10, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
175s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 11, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
175s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 12, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
175s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 13, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
175s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 14, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
175s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 15, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
175s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 16, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
175s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 17, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
175s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 18, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
175s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 19, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
175s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
175s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffb050e540 (FpiDeviceEgisMoc at 0x1d4f700)>, 20, <FPrint.Print object at 0x3ffb0513d00 (FpPrint at 0x1d5a0d0)>, None, None)
175s enroll new finger done
175s listing - device should have 2 prints
175s deleting first print
175s delete done
175s listing - device should only have second print
175s clear device storage
175s clear done
175s listing - device should be empty
175s ** (umockdev-run:2545): DEBUG: 05:03:05.994: umockdev.vala:154: Removing test bed /tmp/umockdev.04A312
175s (umockdev-run:2545): GLib-DEBUG: 05:03:05.997: unsetenv() is not thread-safe and should not be used after threads are created
175s PASS: libfprint-2/driver-egismoc-0586.test
175s Running test: libfprint-2/driver-upektc_img.test
175s ** (umockdev-run:2557): DEBUG: 05:03:06.030: umockdev.vala:127: Created udev test bed /tmp/umockdev.3SKC22
175s ** (umockdev-run:2557): DEBUG: 05:03:06.031: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3
175s ** (umockdev-run:2557): DEBUG: 05:03:06.032: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.3 (subsystem usb)
175s ** (umockdev-run:2557): DEBUG: 05:03:06.033: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3SKC22/dev/bus/usb/001/003
175s ** (umockdev-run:2557): DEBUG: 05:03:06.033: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1/1-1
175s ** (umockdev-run:2557): DEBUG: 05:03:06.035: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1/1-1 (subsystem usb)
175s ** (umockdev-run:2557): DEBUG: 05:03:06.036: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3SKC22/dev/bus/usb/001/002
175s ** (umockdev-run:2557): DEBUG: 05:03:06.036: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0/usb1
175s ** (umockdev-run:2557): DEBUG: 05:03:06.036: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0/usb1 (subsystem usb)
175s ** (umockdev-run:2557): DEBUG: 05:03:06.038: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3SKC22/dev/bus/usb/001/001
175s ** (umockdev-run:2557): DEBUG: 05:03:06.038: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1a.0
175s ** (umockdev-run:2557): DEBUG: 05:03:06.038: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1a.0 (subsystem pci)
175s (process:2561): libfprint-context-DEBUG: 05:03:06.097: Initializing FpContext (libfprint version 1.94.9+tod1)
175s (process:2561): libfprint-tod-DEBUG: 05:03:06.097: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
175s (process:2561): libfprint-context-DEBUG: 05:03:06.098: No driver found for USB device 8087:0020
175s (process:2561): libfprint-context-DEBUG: 05:03:06.098: No driver found for USB device 1D6B:0002
175s (process:2561): libfprint-device-DEBUG: 05:03:06.099: Device reported probe completion
175s (process:2561): libfprint-device-DEBUG: 05:03:06.099: Completing action FPI_DEVICE_ACTION_PROBE in idle!
175s (process:2561): libfprint-device-DEBUG: 05:03:06.099: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.100: Image device open completed
175s (process:2561): libfprint-device-DEBUG: 05:03:06.100: Device reported open completion
175s (process:2561): libfprint-device-DEBUG: 05:03:06.100: Completing action FPI_DEVICE_ACTION_OPEN in idle!
175s (process:2561): libfprint-device-DEBUG: 05:03:06.100: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s (process:2561): libfprint-device-DEBUG: 05:03:06.100: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.100: Activating image device
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.100: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.100: [upektc_img] ACTIVATE_NUM_STATES entering state 0
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.100: [upektc_img] ACTIVATE_NUM_STATES entering state 1
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.101: [upektc_img] ACTIVATE_NUM_STATES entering state 2
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.101: [upektc_img] ACTIVATE_NUM_STATES entering state 3
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.101: [upektc_img] ACTIVATE_NUM_STATES entering state 4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.102: [upektc_img] ACTIVATE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.102: [upektc_img] ACTIVATE_NUM_STATES entering state 6
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.102: [upektc_img] ACTIVATE_NUM_STATES entering state 7
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.102: [upektc_img] ACTIVATE_NUM_STATES entering state 8
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.103: [upektc_img] ACTIVATE_NUM_STATES entering state 9
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.103: [upektc_img] ACTIVATE_NUM_STATES entering state 10
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.103: [upektc_img] ACTIVATE_NUM_STATES entering state 11
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.104: Sensor type : TCS4x, width x height: 192 x 512
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.104: [upektc_img] ACTIVATE_NUM_STATES completed successfully
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.104: Image device activation completed
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.104: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.104: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
175s (process:2561): libfprint-device-DEBUG: 05:03:06.104: Device reported finger status change: FP_FINGER_STATUS_NEEDED
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.104: [upektc_img] CAPTURE_NUM_STATES entering state 0
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.104: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.104: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.104: 18th byte is 0c
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.104: [upektc_img] CAPTURE_NUM_STATES entering state 3
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.105: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.105: request completed, len: 0040
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.105: [upektc_img] CAPTURE_NUM_STATES entering state 4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.105: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.106: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.106: 18th byte is 00
175s (process:2561): libfprint-device-DEBUG: 05:03:06.106: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.106: [upektc_img] CAPTURE_NUM_STATES entering state 3
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.106: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.106: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.106: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.106: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.106: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.107: request completed, len: 07c4
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.107: Image device reported finger status: on
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.107: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.107: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.107: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.107: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.107: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.107: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.107: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.107: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.107: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.108: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.108: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.108: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.108: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.108: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.109: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.109: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.109: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.109: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.109: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.109: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.109: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.109: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.109: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.110: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.110: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.110: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.110: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.110: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.110: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.110: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.111: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.111: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.111: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.111: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.111: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.111: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.111: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.112: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.112: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.112: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.112: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.112: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.112: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.112: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.113: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.113: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.113: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.113: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.113: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.113: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.113: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.113: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.114: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.114: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.114: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.114: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.114: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.114: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.114: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.114: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.114: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.114: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.114: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.115: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.115: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.115: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.115: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.115: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.115: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.115: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.116: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.116: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.116: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.116: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.116: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.116: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.116: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.117: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.117: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.117: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.117: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.117: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.117: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.117: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.118: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.118: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.118: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.118: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.118: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.118: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.118: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.118: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.118: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.119: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.119: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.119: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.119: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.119: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.119: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.119: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.120: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.120: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.120: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.120: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.120: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.120: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.120: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.120: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.121: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.121: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.121: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.121: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.121: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.121: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.121: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.122: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.122: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.122: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.122: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.122: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.122: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.122: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.123: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.123: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.123: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.123: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.123: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.123: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.123: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.123: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.123: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.123: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.123: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.124: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.124: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.124: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.124: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.124: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.124: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.124: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.125: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.125: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.125: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.125: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.125: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.125: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.125: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.125: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.125: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.126: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.126: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.126: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.126: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.126: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.126: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.126: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.126: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.127: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.127: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.127: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.127: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.127: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.127: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.127: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.128: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.128: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.128: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.128: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.128: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.128: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.128: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.128: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.128: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.128: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.128: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.129: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.129: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.129: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.129: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.129: response_size is 2052, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.129: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.129: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.130: request completed, len: 07c4
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.130: [upektc_img] CAPTURE_NUM_STATES entering state 5
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.130: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.130: request completed, len: 0040
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.130: response_size is 186, actual_length is 64
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.130: Waiting for rest of transfer
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.130: [upektc_img] CAPTURE_NUM_STATES entering state 1
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.131: request completed, len: 007a
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.131: Image size is 55296
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.131: Image device captured an image
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.131: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
175s (process:2561): libfprint-device-DEBUG: 05:03:06.131: Device reported finger status change: FP_FINGER_STATUS_PRESENT
175s (process:2561): libfprint-device-DEBUG: 05:03:06.131: Device reported finger status change: FP_FINGER_STATUS_NONE
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.131: Image device reported finger status: off
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.131: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.131: Deactivating image device
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.131: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.131: [upektc_img] CAPTURE_NUM_STATES completed successfully
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.131: [upektc_img] DEACTIVATE_NUM_STATES entering state 0
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.131: [upektc_img] DEACTIVATE_NUM_STATES entering state 1
175s (process:2561): libfprint-SSM-DEBUG: 05:03:06.131: [upektc_img] DEACTIVATE_NUM_STATES completed successfully
175s (process:2561): libfprint-upektc_img-DEBUG: 05:03:06.131: Deactivate completed
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.131: Image device deactivation completed
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.131: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
175s (process:2561): libfprint-image-DEBUG: 05:03:06.142: Minutiae scan completed in 0.011013 secs
175s (process:2561): libfprint-device-DEBUG: 05:03:06.142: Device reported capture completion
175s (process:2561): libfprint-device-DEBUG: 05:03:06.142: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
175s (process:2561): libfprint-device-DEBUG: 05:03:06.142: Updated temperature model after 0.04 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
175s (process:2561): libfprint-image_device-DEBUG: 05:03:06.142: Image device close completed
175s (process:2561): libfprint-device-DEBUG: 05:03:06.142: Device reported close completion
175s (process:2561): libfprint-device-DEBUG: 05:03:06.142: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
175s (process:2561): libfprint-device-DEBUG: 05:03:06.142: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
175s ** (umockdev-run:2557): DEBUG: 05:03:06.223: umockdev.vala:154: Removing test bed /tmp/umockdev.3SKC22
175s (umockdev-run:2557): GLib-DEBUG: 05:03:06.226: unsetenv() is not thread-safe and should not be used after threads are created
175s Comparing PNGs /tmp/libfprint-umockdev-test-z5zfsjac/capture.png and /usr/share/installed-tests/libfprint-2/upektc_img/capture.png
175s PASS: libfprint-2/driver-upektc_img.test
175s Running test: libfprint-2/virtual-device.test
175s (process:2568): libfprint-context-DEBUG: 05:03:06.323: Initializing FpContext (libfprint version 1.94.9+tod1)
175s (process:2568): libfprint-tod-DEBUG: 05:03:06.323: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
175s (process:2568): libfprint-context-DEBUG: 05:03:06.324: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-9y6nijdp/virtual-device.socket
175s (process:2568): libfprint-context-DEBUG: 05:03:06.324: created
175s (process:2568): libfprint-device-DEBUG: 05:03:06.324: Device reported probe completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.324: Completing action FPI_DEVICE_ACTION_PROBE in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.324: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s test_capture_unsupported (__main__.VirtualDevice.test_capture_unsupported) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.324: 53073615: ../libfprint/drivers/virtual-device.c:387
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.325: 53073669: ../libfprint/drivers/virtual-device-listener.c:153
175s (process:2568): libfprint-device-DEBUG: 05:03:06.325: Device reported open completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.325: Completing action FPI_DEVICE_ACTION_OPEN in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.325: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.325: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.325: Got instructions of length 16
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.325: Received command SET_KEEP_ALIVE 0
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.325: Keep alive toggled: 0
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.325: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.325: Got instructions of length 19
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.325: Received command SET_ENROLL_STAGES 5
175s (process:2568): libfprint-device-DEBUG: 05:03:06.325: Device reported close completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.325: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.325: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s ok
175s test_change_enroll_stages (__main__.VirtualDevice.test_change_enroll_stages) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.325: 53074406: ../libfprint/drivers/virtual-device.c:387
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.325: 53074424: ../libfprint/drivers/virtual-device-listener.c:153
175s (process:2568): libfprint-device-DEBUG: 05:03:06.325: Device reported open completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.325: Completing action FPI_DEVICE_ACTION_OPEN in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.325: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.325: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.325: Got instructions of length 20
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.325: Received command SET_ENROLL_STAGES 20
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.326: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.326: Got instructions of length 19
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.326: Received command SET_ENROLL_STAGES 1
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.326: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.326: Got instructions of length 19
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.326: Received command SET_ENROLL_STAGES 0
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.328: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.328: Got instructions of length 16
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.328: Received command SET_KEEP_ALIVE 0
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.328: Keep alive toggled: 0
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.328: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.328: Got instructions of length 19
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.328: Received command SET_ENROLL_STAGES 5
175s (process:2568): libfprint-device-DEBUG: 05:03:06.328: Device reported close completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.328: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.328: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s ok
175s test_change_scan_type (__main__.VirtualDevice.test_change_scan_type) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.328: 53077135: ../libfprint/drivers/virtual-device.c:387
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.328: 53077139: ../libfprint/drivers/virtual-device-listener.c:153
175s (process:2568): libfprint-device-DEBUG: 05:03:06.328: Device reported open completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.328: Completing action FPI_DEVICE_ACTION_OPEN in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.328: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.328: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.328: Got instructions of length 19
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.328: Received command SET_SCAN_TYPE press
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.328: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.328: Got instructions of length 19
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.328: Received command SET_SCAN_TYPE swipe
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.328: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.328: Got instructions of length 25
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.329: Received command SET_SCAN_TYPE eye-contact
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.329: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.329: Got instructions of length 16
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.329: Received command SET_KEEP_ALIVE 0
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.329: Keep alive toggled: 0
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.329: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.329: Got instructions of length 19
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.329: Received command SET_ENROLL_STAGES 5
175s (process:2568): libfprint-device-DEBUG: 05:03:06.329: Device reported close completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.329: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.329: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s ok
175s test_close_error (__main__.VirtualDevice.test_close_error) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.329: 53078056: ../libfprint/drivers/virtual-device.c:387
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.329: 53078061: ../libfprint/drivers/virtual-device-listener.c:153
175s (process:2568): libfprint-device-DEBUG: 05:03:06.329: Device reported open completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.329: Completing action FPI_DEVICE_ACTION_OPEN in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.329: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.329: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.329: Got instructions of length 9
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.329: Received command SLEEP 100
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.329: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.329: Got instructions of length 7
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.329: Received command ERROR 4
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.329: Processing command SLEEP 100
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.329: Sleeping 100ms
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.430: Sleeping completed
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.430: Processing command ERROR 4
175s (process:2568): libfprint-device-DEBUG: 05:03:06.430: Device reported close completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.430: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.430: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s ok
175s test_close_while_opening (__main__.VirtualDevice.test_close_while_opening) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.430: 53179501: ../libfprint/drivers/virtual-device.c:387
175s (process:2568): libfprint-device-DEBUG: 05:03:06.430: Device reported open completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.430: Completing action FPI_DEVICE_ACTION_OPEN in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.430: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.431: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.431: Got instructions of length 16
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.431: Received command SET_KEEP_ALIVE 1
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.431: Keep alive toggled: 1
175s (process:2568): libfprint-device-DEBUG: 05:03:06.431: Device reported close completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.431: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.431: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.431: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.431: Got instructions of length 9
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.431: Received command SLEEP 500
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.431: 53179874: ../libfprint/drivers/virtual-device.c:387
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.431: Processing command SLEEP 500
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.431: Sleeping 500ms
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.931: Sleeping completed
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.931: 53680638: ../libfprint/drivers/virtual-device.c:387
175s (process:2568): libfprint-device-DEBUG: 05:03:06.931: Device reported open completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.932: Completing action FPI_DEVICE_ACTION_OPEN in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.932: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.932: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.932: Got instructions of length 16
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.932: Received command SET_KEEP_ALIVE 0
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.932: Keep alive toggled: 0
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.932: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.932: Got instructions of length 19
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.932: Received command SET_ENROLL_STAGES 5
175s (process:2568): libfprint-device-DEBUG: 05:03:06.932: Device reported close completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.932: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.932: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s ok
175s test_delayed_open (__main__.VirtualDevice.test_delayed_open) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.932: 53681426: ../libfprint/drivers/virtual-device.c:387
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.932: 53681432: ../libfprint/drivers/virtual-device-listener.c:153
175s (process:2568): libfprint-device-DEBUG: 05:03:06.932: Device reported open completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.932: Completing action FPI_DEVICE_ACTION_OPEN in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.932: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.932: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.932: Got instructions of length 16
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.932: Received command IGNORED_COMMAND 
175s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:06.932: Got a new connection!
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.933: Got instructions of length 9
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.933: Received command SLEEP 500
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.933: Processing command IGNORED_COMMAND 
175s (process:2568): libfprint-device-DEBUG: 05:03:06.933: Device reported close completion
175s (process:2568): libfprint-device-DEBUG: 05:03:06.933: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
175s (process:2568): libfprint-device-DEBUG: 05:03:06.933: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.933: 53681878: ../libfprint/drivers/virtual-device.c:387
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.933: Processing command SLEEP 500
175s (process:2568): libfprint-virtual_device-DEBUG: 05:03:06.933: Sleeping 500ms
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.433: Sleeping completed
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.433: 54182587: ../libfprint/drivers/virtual-device.c:387
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.433: 54182608: ../libfprint/drivers/virtual-device-listener.c:153
176s (process:2568): libfprint-device-DEBUG: 05:03:07.434: Device reported open completion
176s (process:2568): libfprint-device-DEBUG: 05:03:07.434: Completing action FPI_DEVICE_ACTION_OPEN in idle!
176s (process:2568): libfprint-device-DEBUG: 05:03:07.434: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.434: Got a new connection!
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.434: Got instructions of length 16
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.434: Received command SET_KEEP_ALIVE 0
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.434: Keep alive toggled: 0
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.434: Got a new connection!
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.434: Got instructions of length 19
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.434: Received command SET_ENROLL_STAGES 5
176s (process:2568): libfprint-device-DEBUG: 05:03:07.434: Device reported close completion
176s (process:2568): libfprint-device-DEBUG: 05:03:07.434: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
176s (process:2568): libfprint-device-DEBUG: 05:03:07.434: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
176s ok
176s test_delayed_open_with_keep_alive (__main__.VirtualDevice.test_delayed_open_with_keep_alive) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.434: 54183369: ../libfprint/drivers/virtual-device.c:387
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.434: 54183372: ../libfprint/drivers/virtual-device-listener.c:153
176s (process:2568): libfprint-device-DEBUG: 05:03:07.434: Device reported open completion
176s (process:2568): libfprint-device-DEBUG: 05:03:07.434: Completing action FPI_DEVICE_ACTION_OPEN in idle!
176s (process:2568): libfprint-device-DEBUG: 05:03:07.434: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.434: Got a new connection!
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.434: Got instructions of length 16
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.434: Received command SET_KEEP_ALIVE 1
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.434: Keep alive toggled: 1
176s (process:2568): libfprint-device-DEBUG: 05:03:07.434: Device reported close completion
176s (process:2568): libfprint-device-DEBUG: 05:03:07.434: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
176s (process:2568): libfprint-device-DEBUG: 05:03:07.434: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.434: Got a new connection!
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.434: Got instructions of length 9
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.434: Received command SLEEP 500
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.434: 54183554: ../libfprint/drivers/virtual-device.c:387
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.434: Processing command SLEEP 500
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.434: Sleeping 500ms
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.935: Sleeping completed
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.935: 54684350: ../libfprint/drivers/virtual-device.c:387
176s (process:2568): libfprint-device-DEBUG: 05:03:07.935: Device reported open completion
176s (process:2568): libfprint-device-DEBUG: 05:03:07.935: Completing action FPI_DEVICE_ACTION_OPEN in idle!
176s (process:2568): libfprint-device-DEBUG: 05:03:07.935: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.936: Got a new connection!
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.936: Got instructions of length 16
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.936: Received command SET_KEEP_ALIVE 0
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.936: Keep alive toggled: 0
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.936: Got a new connection!
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.936: Got instructions of length 19
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.936: Received command SET_ENROLL_STAGES 5
176s (process:2568): libfprint-device-DEBUG: 05:03:07.936: Device reported close completion
176s (process:2568): libfprint-device-DEBUG: 05:03:07.936: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
176s (process:2568): libfprint-device-DEBUG: 05:03:07.936: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
176s ok
176s test_device_features (__main__.VirtualDevice.test_device_features) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.936: 54685239: ../libfprint/drivers/virtual-device.c:387
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.936: 54685249: ../libfprint/drivers/virtual-device-listener.c:153
176s (process:2568): libfprint-device-DEBUG: 05:03:07.936: Device reported open completion
176s (process:2568): libfprint-device-DEBUG: 05:03:07.936: Completing action FPI_DEVICE_ACTION_OPEN in idle!
176s (process:2568): libfprint-device-DEBUG: 05:03:07.936: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.936: Got a new connection!
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.937: Got instructions of length 16
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.937: Received command SET_KEEP_ALIVE 0
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.937: Keep alive toggled: 0
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.937: Got a new connection!
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.937: Got instructions of length 19
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.937: Received command SET_ENROLL_STAGES 5
176s (process:2568): libfprint-device-DEBUG: 05:03:07.937: Device reported close completion
176s (process:2568): libfprint-device-DEBUG: 05:03:07.937: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
176s (process:2568): libfprint-device-DEBUG: 05:03:07.937: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
176s ok
176s test_device_properties (__main__.VirtualDevice.test_device_properties) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.937: 54685864: ../libfprint/drivers/virtual-device.c:387
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.937: 54685872: ../libfprint/drivers/virtual-device-listener.c:153
176s (process:2568): libfprint-device-DEBUG: 05:03:07.937: Device reported open completion
176s (process:2568): libfprint-device-DEBUG: 05:03:07.937: Completing action FPI_DEVICE_ACTION_OPEN in idle!
176s (process:2568): libfprint-device-DEBUG: 05:03:07.937: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.937: Got a new connection!
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.937: Got instructions of length 16
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.937: Received command SET_KEEP_ALIVE 0
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.937: Keep alive toggled: 0
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.937: Got a new connection!
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.937: Got instructions of length 19
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.937: Received command SET_ENROLL_STAGES 5
176s (process:2568): libfprint-device-DEBUG: 05:03:07.937: Device reported close completion
176s (process:2568): libfprint-device-DEBUG: 05:03:07.937: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
176s (process:2568): libfprint-device-DEBUG: 05:03:07.937: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
176s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:463: DeprecationWarning: FPrint.Device.supports_identify is deprecated
176s   self.assertFalse(self.dev.supports_identify())
176s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:464: DeprecationWarning: FPrint.Device.supports_capture is deprecated
176s   self.assertFalse(self.dev.supports_capture())
176s /usr/libexec/installed-tests/libfprint-2/virtual-device.py:465: DeprecationWarning: FPrint.Device.has_storage is deprecated
176s   self.assertFalse(self.dev.has_storage())
176s ok
176s test_device_sleep (__main__.VirtualDevice.test_device_sleep) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.937: 54686370: ../libfprint/drivers/virtual-device.c:387
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.937: 54686379: ../libfprint/drivers/virtual-device-listener.c:153
176s (process:2568): libfprint-device-DEBUG: 05:03:07.937: Device reported open completion
176s (process:2568): libfprint-device-DEBUG: 05:03:07.937: Completing action FPI_DEVICE_ACTION_OPEN in idle!
176s (process:2568): libfprint-device-DEBUG: 05:03:07.937: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
176s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:07.937: Got a new connection!
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.937: Got instructions of length 10
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.937: Received command SLEEP 1500
176s (process:2568): libfprint-device-DEBUG: 05:03:07.938: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.938: Processing command SLEEP 1500
176s (process:2568): libfprint-virtual_device-DEBUG: 05:03:07.938: Sleeping 1500ms
177s (process:2568): libfprint-device-DEBUG: 05:03:08.235: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
177s (process:2568): libfprint-device-DEBUG: 05:03:08.238: Idle cancelling on ongoing operation!
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.238: Got cancellation!
177s (process:2568): libfprint-device-DEBUG: 05:03:08.238: Device reported finger status change: FP_FINGER_STATUS_NEEDED
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.238: Virtual device scan failed with error: Operation was cancelled
177s (process:2568): libfprint-device-DEBUG: 05:03:08.238: Device reported verify completion
177s (process:2568): libfprint-device-DEBUG: 05:03:08.238: Device reported finger status change: FP_FINGER_STATUS_NONE
177s (process:2568): libfprint-device-DEBUG: 05:03:08.238: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
177s (process:2568): libfprint-device-DEBUG: 05:03:08.238: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
177s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:08.438: Got a new connection!
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.438: Got instructions of length 16
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.438: Received command SET_KEEP_ALIVE 0
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.438: Keep alive toggled: 0
177s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:08.439: Got a new connection!
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.439: Got instructions of length 19
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.439: Received command SET_ENROLL_STAGES 5
177s (process:2568): libfprint-device-DEBUG: 05:03:08.439: Device reported close completion
177s (process:2568): libfprint-device-DEBUG: 05:03:08.439: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
177s (process:2568): libfprint-device-DEBUG: 05:03:08.439: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
177s ok
177s test_device_sleep_before_completing_verify (__main__.VirtualDevice.test_device_sleep_before_completing_verify) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.439: 55187915: ../libfprint/drivers/virtual-device.c:387
177s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:08.439: 55187927: ../libfprint/drivers/virtual-device-listener.c:153
177s (process:2568): libfprint-device-DEBUG: 05:03:08.439: Device reported open completion
177s (process:2568): libfprint-device-DEBUG: 05:03:08.439: Completing action FPI_DEVICE_ACTION_OPEN in idle!
177s (process:2568): libfprint-device-DEBUG: 05:03:08.439: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
177s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:08.439: Got a new connection!
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.439: Got instructions of length 14
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.439: Received command SCAN foo-print
177s (process:2568): libfprint-device-DEBUG: 05:03:08.439: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.439: Processing command SCAN foo-print
177s (process:2568): libfprint-device-DEBUG: 05:03:08.439: Device reported finger status change: FP_FINGER_STATUS_NEEDED
177s (process:2568): libfprint-device-DEBUG: 05:03:08.439: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
177s (process:2568): libfprint-device-DEBUG: 05:03:08.439: Device reported finger status change: FP_FINGER_STATUS_NEEDED
177s (process:2568): libfprint-device-DEBUG: 05:03:08.439: Device reported enroll progress, reported 1 of 5 have been completed
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.439: Sleeping completed
177s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:08.439: Got a new connection!
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.439: Got instructions of length 14
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.439: Received command SCAN foo-print
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.439: Processing command SCAN foo-print
177s (process:2568): libfprint-device-DEBUG: 05:03:08.439: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
177s (process:2568): libfprint-device-DEBUG: 05:03:08.439: Device reported finger status change: FP_FINGER_STATUS_NEEDED
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Device reported enroll progress, reported 2 of 5 have been completed
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Sleeping completed
177s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:08.440: Got a new connection!
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Got instructions of length 14
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Received command SCAN foo-print
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Processing command SCAN foo-print
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Device reported finger status change: FP_FINGER_STATUS_NEEDED
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Device reported enroll progress, reported 3 of 5 have been completed
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Sleeping completed
177s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:08.440: Got a new connection!
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Got instructions of length 14
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Received command SCAN foo-print
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Processing command SCAN foo-print
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Device reported finger status change: FP_FINGER_STATUS_NEEDED
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Device reported enroll progress, reported 4 of 5 have been completed
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Sleeping completed
177s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:08.440: Got a new connection!
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Got instructions of length 14
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Received command SCAN foo-print
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Processing command SCAN foo-print
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Device reported finger status change: FP_FINGER_STATUS_NEEDED
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Device reported enroll progress, reported 5 of 5 have been completed
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Device reported enroll completion
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Device reported finger status change: FP_FINGER_STATUS_NONE
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Print for finger FP_FINGER_LEFT_RING enrolled
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
177s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:08.440: Got a new connection!
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Got instructions of length 9
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Received command SLEEP 100
177s (process:2568): libfprint-device-DEBUG: 05:03:08.440: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Processing command SLEEP 100
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Sleeping 100ms
177s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:08.440: Got a new connection!
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Got instructions of length 14
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Received command SCAN bar-print
177s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:08.440: Got a new connection!
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Got instructions of length 9
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.440: Received command SLEEP 800
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.540: Sleeping completed
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.540: Processing command SCAN bar-print
177s (process:2568): libfprint-device-DEBUG: 05:03:08.540: Device reported finger status change: FP_FINGER_STATUS_NEEDED
177s (process:2568): libfprint-device-DEBUG: 05:03:08.540: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.540: Virtual device scanned print bar-print
177s (process:2568): libfprint-device-DEBUG: 05:03:08.540: Device reported verify result
177s (process:2568): libfprint-device-DEBUG: 05:03:08.540: Device reported finger status change: FP_FINGER_STATUS_NEEDED
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.540: Processing command SLEEP 800
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.540: Sleeping 800ms
177s (process:2568): libfprint-virtual_device-DEBUG: 05:03:08.540: Sleeping now, command queued for later: SCAN bar-print
178s Executing: libfprint-2/virtual-device.test
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.341: Sleeping completed
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.341: Processing command SCAN bar-print
178s (process:2568): libfprint-device-DEBUG: 05:03:09.341: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.342: Virtual device scanned print bar-print
178s (process:2568): libfprint-device-DEBUG: 05:03:09.342: Device reported finger status change: FP_FINGER_STATUS_NEEDED
178s (process:2568): libfprint-device-DEBUG: 05:03:09.342: Device reported verify completion
178s (process:2568): libfprint-device-DEBUG: 05:03:09.342: Device reported finger status change: FP_FINGER_STATUS_NONE
178s (process:2568): libfprint-device-DEBUG: 05:03:09.342: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
178s (process:2568): libfprint-device-DEBUG: 05:03:09.342: Updated temperature model after 0.90 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
178s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:09.342: Got a new connection!
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.342: Got instructions of length 16
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.342: Received command SET_KEEP_ALIVE 0
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.342: Keep alive toggled: 0
178s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:09.342: Got a new connection!
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.342: Got instructions of length 19
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.342: Received command SET_ENROLL_STAGES 5
178s (process:2568): libfprint-device-DEBUG: 05:03:09.342: Device reported close completion
178s (process:2568): libfprint-device-DEBUG: 05:03:09.342: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
178s (process:2568): libfprint-device-DEBUG: 05:03:09.342: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
178s Enroll done
178s ok
178s test_device_sleep_on_cancellation (__main__.VirtualDevice.test_device_sleep_on_cancellation) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.342: 56091508: ../libfprint/drivers/virtual-device.c:387
178s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:09.342: 56091519: ../libfprint/drivers/virtual-device-listener.c:153
178s (process:2568): libfprint-device-DEBUG: 05:03:09.342: Device reported open completion
178s (process:2568): libfprint-device-DEBUG: 05:03:09.342: Completing action FPI_DEVICE_ACTION_OPEN in idle!
178s (process:2568): libfprint-device-DEBUG: 05:03:09.342: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
178s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:09.343: Got a new connection!
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.343: Got instructions of length 26
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.343: Received command SET_CANCELLATION_ENABLED 0
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.343: Cancellation support toggled: 0
178s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:09.343: Got a new connection!
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.343: Got instructions of length 10
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.343: Received command SLEEP 1500
178s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:09.343: Got a new connection!
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.343: Got instructions of length 14
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.343: Received command SCAN foo-print
178s (process:2568): libfprint-device-DEBUG: 05:03:09.343: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.343: Processing command SLEEP 1500
178s (process:2568): libfprint-virtual_device-DEBUG: 05:03:09.343: Sleeping 1500ms
178s (process:2568): libfprint-device-DEBUG: 05:03:09.643: Idle cancelling on ongoing operation!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.844: Sleeping completed
179s (process:2568): libfprint-device-DEBUG: 05:03:10.844: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.844: Virtual device scan failed with error: Operation was cancelled
179s (process:2568): libfprint-device-DEBUG: 05:03:10.844: Device reported verify completion
179s (process:2568): libfprint-device-DEBUG: 05:03:10.844: Device reported finger status change: FP_FINGER_STATUS_NONE
179s (process:2568): libfprint-device-DEBUG: 05:03:10.844: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
179s (process:2568): libfprint-device-DEBUG: 05:03:10.844: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.844: Processing command SCAN foo-print
179s (process:2568): libfprint-device-DEBUG: 05:03:10.845: Device reported close completion
179s (process:2568): libfprint-device-DEBUG: 05:03:10.845: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
179s (process:2568): libfprint-device-DEBUG: 05:03:10.845: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
179s ok
179s test_enroll (__main__.VirtualDevice.test_enroll) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.845: 57594049: ../libfprint/drivers/virtual-device.c:387
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.845: 57594060: ../libfprint/drivers/virtual-device-listener.c:153
179s (process:2568): libfprint-device-DEBUG: 05:03:10.845: Device reported open completion
179s (process:2568): libfprint-device-DEBUG: 05:03:10.845: Completing action FPI_DEVICE_ACTION_OPEN in idle!
179s (process:2568): libfprint-device-DEBUG: 05:03:10.845: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.845: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.845: Got instructions of length 14
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.845: Received command SCAN testprint
179s (process:2568): libfprint-device-DEBUG: 05:03:10.845: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.845: Processing command SCAN testprint
179s (process:2568): libfprint-device-DEBUG: 05:03:10.845: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.845: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported enroll progress, reported 1 of 5 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Sleeping completed
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.846: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Got instructions of length 14
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Received command SCAN testprint
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Processing command SCAN testprint
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported enroll progress, reported 2 of 5 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Sleeping completed
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.846: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Got instructions of length 14
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Received command SCAN testprint
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Processing command SCAN testprint
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported enroll progress, reported 3 of 5 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Sleeping completed
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.846: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Got instructions of length 14
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Received command SCAN testprint
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Processing command SCAN testprint
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported enroll progress, reported 4 of 5 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Sleeping completed
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.846: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Got instructions of length 14
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Received command SCAN testprint
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Processing command SCAN testprint
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported enroll progress, reported 5 of 5 have been completed
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported enroll completion
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Device reported finger status change: FP_FINGER_STATUS_NONE
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Print for finger FP_FINGER_LEFT_LITTLE enrolled
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
179s (process:2568): libfprint-device-DEBUG: 05:03:10.846: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.846: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Got instructions of length 16
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Received command SET_KEEP_ALIVE 0
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.846: Keep alive toggled: 0
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.847: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Got instructions of length 19
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Received command SET_ENROLL_STAGES 5
179s (process:2568): libfprint-device-DEBUG: 05:03:10.847: Device reported close completion
179s (process:2568): libfprint-device-DEBUG: 05:03:10.847: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
179s (process:2568): libfprint-device-DEBUG: 05:03:10.847: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
179s Enroll done
179s ok
179s test_enroll_script (__main__.VirtualDevice.test_enroll_script) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: 57595838: ../libfprint/drivers/virtual-device.c:387
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.847: 57595848: ../libfprint/drivers/virtual-device-listener.c:153
179s (process:2568): libfprint-device-DEBUG: 05:03:10.847: Device reported open completion
179s (process:2568): libfprint-device-DEBUG: 05:03:10.847: Completing action FPI_DEVICE_ACTION_OPEN in idle!
179s (process:2568): libfprint-device-DEBUG: 05:03:10.847: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.847: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Got instructions of length 19
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Received command SET_ENROLL_STAGES 8
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.847: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Got instructions of length 13
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Received command SCAN print-id
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.847: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Got instructions of length 13
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Received command SCAN print-id
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.847: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Got instructions of length 7
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Received command RETRY 1
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.847: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Got instructions of length 13
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Received command SCAN print-id
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.847: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Got instructions of length 7
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Received command RETRY 3
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.847: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Got instructions of length 13
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Received command SCAN print-id
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.847: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Got instructions of length 7
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Received command RETRY 2
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.847: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Got instructions of length 13
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Received command SCAN print-id
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.847: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Got instructions of length 8
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Received command SLEEP 10
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.847: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Got instructions of length 8
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Received command SLEEP 20
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.847: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Got instructions of length 7
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.847: Received command RETRY 0
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.848: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Got instructions of length 7
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Received command RETRY 3
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.848: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Got instructions of length 13
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Received command SCAN print-id
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.848: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Got instructions of length 15
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Received command SCAN another-id
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.848: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Got instructions of length 13
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Received command SCAN print-id
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.848: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Got instructions of length 13
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Received command SCAN print-id
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Processing command SCAN print-id
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported enroll progress, reported 1 of 8 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Sleeping completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Processing command SCAN print-id
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported enroll progress, reported 2 of 8 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Sleeping completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Processing command RETRY 1
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported enroll progress, reported 2 of 8 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Sleeping completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Processing command SCAN print-id
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported enroll progress, reported 3 of 8 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Sleeping completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Processing command RETRY 3
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported enroll progress, reported 3 of 8 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Sleeping completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Processing command SCAN print-id
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported enroll progress, reported 4 of 8 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Sleeping completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Processing command RETRY 2
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported enroll progress, reported 4 of 8 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Sleeping completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Processing command SCAN print-id
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.848: Device reported enroll progress, reported 5 of 8 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Processing command SLEEP 10
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.848: Sleeping 10ms
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.858: Sleeping completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.858: Processing command SLEEP 20
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.858: Sleeping 20ms
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.878: Sleeping completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.878: Processing command RETRY 0
179s (process:2568): libfprint-device-DEBUG: 05:03:10.878: Device reported enroll progress, reported 5 of 8 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.878: Sleeping completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.878: Processing command RETRY 3
179s (process:2568): libfprint-device-DEBUG: 05:03:10.878: Device reported enroll progress, reported 5 of 8 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.878: Sleeping completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.878: Processing command SCAN print-id
179s (process:2568): libfprint-device-DEBUG: 05:03:10.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
179s (process:2568): libfprint-device-DEBUG: 05:03:10.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.878: Device reported enroll progress, reported 6 of 8 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.878: Sleeping completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.878: Processing command SCAN another-id
179s (process:2568): libfprint-device-DEBUG: 05:03:10.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
179s (process:2568): libfprint-device-DEBUG: 05:03:10.878: Device reported enroll progress, reported 6 of 8 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.878: Sleeping completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.878: Processing command SCAN print-id
179s (process:2568): libfprint-device-DEBUG: 05:03:10.878: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.878: Device reported enroll progress, reported 7 of 8 have been completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Sleeping completed
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Processing command SCAN print-id
179s (process:2568): libfprint-device-DEBUG: 05:03:10.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
179s (process:2568): libfprint-device-DEBUG: 05:03:10.879: Device reported finger status change: FP_FINGER_STATUS_NEEDED
179s (process:2568): libfprint-device-DEBUG: 05:03:10.879: Device reported enroll progress, reported 8 of 8 have been completed
179s (process:2568): libfprint-device-DEBUG: 05:03:10.879: Device reported enroll completion
179s (process:2568): libfprint-device-DEBUG: 05:03:10.879: Device reported finger status change: FP_FINGER_STATUS_NONE
179s (process:2568): libfprint-device-DEBUG: 05:03:10.879: Print for finger FP_FINGER_UNKNOWN enrolled
179s (process:2568): libfprint-device-DEBUG: 05:03:10.879: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
179s (process:2568): libfprint-device-DEBUG: 05:03:10.879: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.879: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Got instructions of length 16
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Received command SET_KEEP_ALIVE 0
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Keep alive toggled: 0
179s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.879: Got a new connection!
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Got instructions of length 19
179s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Received command SET_ENROLL_STAGES 5
179s (process:2568): libfprint-device-DEBUG: 05:03:10.879: Device reported close completion
179s (process:2568): libfprint-device-DEBUG: 05:03:10.879: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.879: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s ok
180s test_enroll_script_interactive (__main__.VirtualDevice.test_enroll_script_interactive) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: 57628144: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.879: 57628155: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:10.879: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.879: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.879: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.879: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Got instructions of length 8
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Received command SLEEP 50
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.879: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Got instructions of length 13
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Received command SCAN print-id
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.879: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Got instructions of length 13
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Received command SCAN print-id
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.879: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Got instructions of length 7
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Received command RETRY 1
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.879: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Got instructions of length 13
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Received command SCAN print-id
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.879: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Got instructions of length 8
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Received command SLEEP 50
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.879: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Got instructions of length 13
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.879: Received command SCAN print-id
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.880: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.880: Got instructions of length 7
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.880: Received command RETRY 2
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.880: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.880: Got instructions of length 15
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.880: Received command SCAN another-id
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.880: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.880: Got instructions of length 13
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.880: Received command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:10.880: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.880: Processing command SLEEP 50
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.880: Sleeping 50ms
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.930: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.930: Processing command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:10.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.930: Device reported enroll progress, reported 1 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.930: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.930: Processing command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:10.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.930: Device reported enroll progress, reported 2 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.930: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.930: Processing command RETRY 1
180s (process:2568): libfprint-device-DEBUG: 05:03:10.930: Device reported enroll progress, reported 2 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.930: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.930: Processing command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:10.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.930: Device reported enroll progress, reported 3 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.930: Processing command SLEEP 50
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.930: Sleeping 50ms
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.980: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.980: Processing command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:10.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.980: Device reported enroll progress, reported 4 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.980: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.980: Processing command RETRY 2
180s (process:2568): libfprint-device-DEBUG: 05:03:10.980: Device reported enroll progress, reported 4 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.980: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.980: Processing command SCAN another-id
180s (process:2568): libfprint-device-DEBUG: 05:03:10.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.980: Device reported enroll progress, reported 4 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.980: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.980: Processing command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:10.980: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.980: Device reported enroll progress, reported 5 of 5 have been completed
180s (process:2568): libfprint-device-DEBUG: 05:03:10.980: Device reported enroll completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.980: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:10.980: Print for finger FP_FINGER_UNKNOWN enrolled
180s (process:2568): libfprint-device-DEBUG: 05:03:10.980: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.980: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.981: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.981: Got instructions of length 16
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.981: Received command SET_KEEP_ALIVE 0
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.981: Keep alive toggled: 0
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.981: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.981: Got instructions of length 19
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.981: Received command SET_ENROLL_STAGES 5
180s (process:2568): libfprint-device-DEBUG: 05:03:10.981: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.981: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.981: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s ok
180s test_enroll_verify_error (__main__.VirtualDevice.test_enroll_verify_error) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.981: 57730218: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.981: 57730231: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:10.981: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.981: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.981: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.981: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.981: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.981: Received command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.981: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.981: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.981: Device reported enroll progress, reported 1 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.981: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.981: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.981: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.981: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.981: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.981: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.981: Device reported enroll progress, reported 2 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.981: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.982: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported enroll progress, reported 3 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.982: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported enroll progress, reported 4 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.982: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported enroll progress, reported 5 of 5 have been completed
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported enroll completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Print for finger FP_FINGER_LEFT_RING enrolled
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.982: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Got instructions of length 7
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Received command ERROR 0
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Processing command ERROR 0
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Virtual device scan failed with error: An unspecified error occurred!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported verify completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.982: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Got instructions of length 16
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Received command SET_KEEP_ALIVE 0
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Keep alive toggled: 0
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.982: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Got instructions of length 19
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Received command SET_ENROLL_STAGES 5
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s Enroll done
180s ok
180s test_enroll_verify_match (__main__.VirtualDevice.test_enroll_verify_match) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: 57731478: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.982: 57731487: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.982: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Received command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.982: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.982: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported enroll progress, reported 1 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.983: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported enroll progress, reported 2 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.983: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported enroll progress, reported 3 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.983: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported enroll progress, reported 4 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.983: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported enroll progress, reported 5 of 5 have been completed
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported enroll completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Print for finger FP_FINGER_LEFT_THUMB enrolled
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.983: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Received command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Virtual device scanned print testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported verify result
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported verify completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.983: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Got instructions of length 16
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Received command SET_KEEP_ALIVE 0
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Keep alive toggled: 0
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.983: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Got instructions of length 19
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: Received command SET_ENROLL_STAGES 5
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s Enroll done
180s ok
180s test_enroll_verify_no_match (__main__.VirtualDevice.test_enroll_verify_no_match) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.983: 57732620: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.983: 57732627: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:10.983: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.984: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Received command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported enroll progress, reported 1 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.984: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported enroll progress, reported 2 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.984: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported enroll progress, reported 3 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.984: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported enroll progress, reported 4 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.984: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported enroll progress, reported 5 of 5 have been completed
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported enroll completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Print for finger FP_FINGER_LEFT_RING enrolled
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.984: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Got instructions of length 18
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Received command SCAN not-testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Processing command SCAN not-testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Virtual device scanned print not-testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported verify result
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported verify completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.984: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.984: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Got instructions of length 16
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Received command SET_KEEP_ALIVE 0
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Keep alive toggled: 0
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.984: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Got instructions of length 19
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.984: Received command SET_ENROLL_STAGES 5
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s Enroll done
180s ok
180s test_enroll_verify_retry (__main__.VirtualDevice.test_enroll_verify_retry) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: 57733736: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.985: 57733743: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.985: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Got instructions of length 7
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Received command RETRY 1
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Processing command RETRY 1
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Virtual device scan failed with error: The swipe was too short, please try again.
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Device reported verify result
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Device reported verify completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.985: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Got instructions of length 16
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Received command SET_KEEP_ALIVE 0
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Keep alive toggled: 0
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.985: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Got instructions of length 19
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Received command SET_ENROLL_STAGES 5
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s ok
180s test_enroll_verify_script (__main__.VirtualDevice.test_enroll_verify_script) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: 57734221: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.985: 57734228: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:10.985: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.985: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Got instructions of length 19
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Received command SET_ENROLL_STAGES 8
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.985: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Got instructions of length 13
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Received command SCAN print-id
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.985: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Got instructions of length 13
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Received command SCAN print-id
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.985: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Got instructions of length 7
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Received command RETRY 1
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.985: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Got instructions of length 13
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Received command SCAN print-id
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.985: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Got instructions of length 7
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.985: Received command RETRY 3
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.986: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Got instructions of length 13
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Received command SCAN print-id
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.986: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Got instructions of length 7
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Received command RETRY 2
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.986: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Got instructions of length 13
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Received command SCAN print-id
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.986: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Got instructions of length 8
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Received command SLEEP 10
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.986: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Got instructions of length 8
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Received command SLEEP 20
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.986: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Got instructions of length 7
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Received command RETRY 0
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.986: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Got instructions of length 7
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Received command RETRY 3
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.986: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Got instructions of length 13
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Received command SCAN print-id
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.986: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Got instructions of length 15
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Received command SCAN another-id
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.986: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Got instructions of length 13
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Received command SCAN print-id
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:10.986: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Got instructions of length 13
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Received command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Processing command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported enroll progress, reported 1 of 8 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Processing command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported enroll progress, reported 2 of 8 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Processing command RETRY 1
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported enroll progress, reported 2 of 8 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Processing command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported enroll progress, reported 3 of 8 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Processing command RETRY 3
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported enroll progress, reported 3 of 8 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Processing command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported enroll progress, reported 4 of 8 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Processing command RETRY 2
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported enroll progress, reported 4 of 8 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Processing command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:10.986: Device reported enroll progress, reported 5 of 8 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Processing command SLEEP 10
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.986: Sleeping 10ms
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.996: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.997: Processing command SLEEP 20
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:10.997: Sleeping 20ms
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Processing command RETRY 0
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported enroll progress, reported 5 of 8 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Processing command RETRY 3
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported enroll progress, reported 5 of 8 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Processing command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported enroll progress, reported 6 of 8 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Processing command SCAN another-id
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported enroll progress, reported 6 of 8 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Processing command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported enroll progress, reported 7 of 8 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Processing command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported enroll progress, reported 8 of 8 have been completed
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported enroll completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Print for finger FP_FINGER_UNKNOWN enrolled
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.017: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Got instructions of length 7
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Received command RETRY 2
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Processing command RETRY 2
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Virtual device scan failed with error: The finger was not centered properly, please try again.
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported verify result
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported verify completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.017: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.017: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Got instructions of length 8
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.017: Received command SLEEP 50
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.018: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.018: Got instructions of length 7
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.018: Received command RETRY 1
180s (process:2568): libfprint-device-DEBUG: 05:03:11.018: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.018: Processing command SLEEP 50
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.018: Sleeping 50ms
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Sleeping completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Processing command RETRY 1
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Virtual device scan failed with error: The swipe was too short, please try again.
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported verify result
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported verify completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.068: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Got instructions of length 15
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Received command SCAN another-id
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Processing command SCAN another-id
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Virtual device scanned print another-id
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported verify result
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported verify completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.068: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Got instructions of length 13
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Received command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Processing command SCAN print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Virtual device scanned print print-id
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported verify result
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported verify completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.068: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Got instructions of length 16
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Received command SET_KEEP_ALIVE 0
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Keep alive toggled: 0
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.068: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Got instructions of length 19
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.068: Received command SET_ENROLL_STAGES 5
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s ok
180s test_enroll_with_retry (__main__.VirtualDevice.test_enroll_with_retry) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: 57817697: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.069: 57817706: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.069: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Received command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported enroll progress, reported 1 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.069: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported enroll progress, reported 2 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.069: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Got instructions of length 7
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Received command RETRY 1
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Processing command RETRY 1
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported enroll progress, reported 2 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.069: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported enroll progress, reported 3 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.069: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported enroll progress, reported 4 of 5 have been completed
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Sleeping completed
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.069: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Received command SCAN testprint
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.069: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported enroll progress, reported 5 of 5 have been completed
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported enroll completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Print for finger FP_FINGER_LEFT_LITTLE enrolled
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.069: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.070: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Got instructions of length 16
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Received command SET_KEEP_ALIVE 0
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Keep alive toggled: 0
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.070: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Got instructions of length 19
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Received command SET_ENROLL_STAGES 5
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s Enroll done
180s ok
180s test_finger_status (__main__.VirtualDevice.test_finger_status) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: 57818837: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.070: 57818844: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.070: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Got instructions of length 8
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Received command FINGER 1
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Processing command FINGER 1
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.070: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Got instructions of length 8
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Received command FINGER 0
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Processing command FINGER 0
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Idle cancelling on ongoing operation!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Got cancellation!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Virtual device scan failed with error: Operation was cancelled
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Device reported verify completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.070: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Got instructions of length 16
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Received command SET_KEEP_ALIVE 0
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Keep alive toggled: 0
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.070: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Got instructions of length 19
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Received command SET_ENROLL_STAGES 5
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s ok
180s test_finger_status_after_sleep (__main__.VirtualDevice.test_finger_status_after_sleep) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: 57819383: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.070: 57819390: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.070: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Got instructions of length 8
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Received command SLEEP 10
180s (process:2568): libfprint-device-DEBUG: 05:03:11.070: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Processing command SLEEP 10
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.070: Sleeping 10ms
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Sleeping completed
180s (process:2568): libfprint-device-DEBUG: 05:03:11.081: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.081: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Got instructions of length 8
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Received command FINGER 1
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Processing command FINGER 1
180s (process:2568): libfprint-device-DEBUG: 05:03:11.081: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.081: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Got instructions of length 8
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Received command FINGER 0
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Processing command FINGER 0
180s (process:2568): libfprint-device-DEBUG: 05:03:11.081: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.081: Idle cancelling on ongoing operation!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Got cancellation!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Virtual device scan failed with error: Operation was cancelled
180s (process:2568): libfprint-device-DEBUG: 05:03:11.081: Device reported verify completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.081: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:11.081: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.081: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.081: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Got instructions of length 16
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Received command SET_KEEP_ALIVE 0
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Keep alive toggled: 0
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.081: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Got instructions of length 19
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Received command SET_ENROLL_STAGES 5
180s (process:2568): libfprint-device-DEBUG: 05:03:11.081: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.081: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.081: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s ok
180s test_identify_unsupported (__main__.VirtualDevice.test_identify_unsupported) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: 57830379: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.081: 57830388: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:11.081: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.081: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.081: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.081: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Got instructions of length 16
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.081: Received command SET_KEEP_ALIVE 0
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Keep alive toggled: 0
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.082: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Got instructions of length 19
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Received command SET_ENROLL_STAGES 5
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s ok
180s test_open_error (__main__.VirtualDevice.test_open_error) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: 57830802: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.082: 57830809: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.082: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Got instructions of length 16
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Received command IGNORED_COMMAND 
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.082: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Got instructions of length 7
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Received command ERROR 5
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Processing command IGNORED_COMMAND 
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: 57831185: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Processing command ERROR 5
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s ok
180s test_open_error_with_keep_alive (__main__.VirtualDevice.test_open_error_with_keep_alive) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: 57831269: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.082: 57831277: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.082: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Got instructions of length 16
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Received command SET_KEEP_ALIVE 1
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Keep alive toggled: 1
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.082: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Got instructions of length 7
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Received command ERROR 5
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: 57831506: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: Processing command ERROR 5
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s ok
180s test_quick_enroll (__main__.VirtualDevice.test_quick_enroll) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.082: 57831583: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.082: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.082: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.083: Got instructions of length 19
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.083: Received command SET_ENROLL_STAGES 1
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.083: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.083: Got instructions of length 14
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.083: Received command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:11.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.083: Processing command SCAN testprint
180s (process:2568): libfprint-device-DEBUG: 05:03:11.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
180s (process:2568): libfprint-device-DEBUG: 05:03:11.083: Device reported finger status change: FP_FINGER_STATUS_NEEDED
180s (process:2568): libfprint-device-DEBUG: 05:03:11.083: Device reported enroll progress, reported 1 of 1 have been completed
180s (process:2568): libfprint-device-DEBUG: 05:03:11.083: Device reported enroll completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.083: Device reported finger status change: FP_FINGER_STATUS_NONE
180s (process:2568): libfprint-device-DEBUG: 05:03:11.083: Print for finger FP_FINGER_LEFT_LITTLE enrolled
180s (process:2568): libfprint-device-DEBUG: 05:03:11.083: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.083: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.083: Got instructions of length 16
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.083: Received command SET_KEEP_ALIVE 0
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.083: Keep alive toggled: 0
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.083: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.083: Got instructions of length 19
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.083: Received command SET_ENROLL_STAGES 5
180s (process:2568): libfprint-device-DEBUG: 05:03:11.083: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.083: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.083: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
180s Enroll done
180s ok
180s (process:2568): libfprint-context-DEBUG: 05:03:11.083: Initializing FpContext (libfprint version 1.94.9+tod1)
180s (process:2568): libfprint-tod-DEBUG: 05:03:11.083: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
180s (process:2568): libfprint-context-DEBUG: 05:03:11.084: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-7vevt91v/virtual-device.socket
180s (process:2568): libfprint-context-DEBUG: 05:03:11.084: created
180s (process:2568): libfprint-device-DEBUG: 05:03:11.084: Device reported probe completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.084: Completing action FPI_DEVICE_ACTION_PROBE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.084: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
180s test_capture (__main__.VirtualDeviceBusyDeviceOperations.test_capture) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.084: 57833209: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.084: 57833223: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:11.084: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.084: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.084: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.084: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.084: Got instructions of length 9
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.084: Received command SLEEP 200
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.084: Processing command SLEEP 200
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.084: Sleeping 200ms
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.285: Sleeping completed
180s (process:2568): libfprint-device-DEBUG: 05:03:11.285: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.285: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.285: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
180s ok
180s test_close (__main__.VirtualDeviceBusyDeviceOperations.test_close) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.285: 58034374: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.285: 58034395: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:11.285: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.285: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.285: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.286: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.286: Got instructions of length 9
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.286: Received command SLEEP 200
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.286: Processing command SLEEP 200
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.286: Sleeping 200ms
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.486: Sleeping completed
180s (process:2568): libfprint-device-DEBUG: 05:03:11.486: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.486: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.486: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
180s ok
180s test_delete_print (__main__.VirtualDeviceBusyDeviceOperations.test_delete_print) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.487: 58235813: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.487: 58235835: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:11.487: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.487: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.487: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.487: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.487: Got instructions of length 9
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.487: Received command SLEEP 200
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.487: Processing command SLEEP 200
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.487: Sleeping 200ms
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.687: Sleeping completed
180s (process:2568): libfprint-device-DEBUG: 05:03:11.688: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.688: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.688: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
180s ok
180s test_enroll (__main__.VirtualDeviceBusyDeviceOperations.test_enroll) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.688: 58437204: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.688: 58437213: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:11.688: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.688: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.688: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.688: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.688: Got instructions of length 9
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.688: Received command SLEEP 200
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.688: Processing command SLEEP 200
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.688: Sleeping 200ms
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.889: Sleeping completed
180s (process:2568): libfprint-device-DEBUG: 05:03:11.889: Device reported close completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.889: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.889: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
180s ok
180s test_identify (__main__.VirtualDeviceBusyDeviceOperations.test_identify) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.890: 58638714: ../libfprint/drivers/virtual-device.c:387
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.890: 58638745: ../libfprint/drivers/virtual-device-listener.c:153
180s (process:2568): libfprint-device-DEBUG: 05:03:11.890: Device reported open completion
180s (process:2568): libfprint-device-DEBUG: 05:03:11.890: Completing action FPI_DEVICE_ACTION_OPEN in idle!
180s (process:2568): libfprint-device-DEBUG: 05:03:11.890: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
180s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:11.890: Got a new connection!
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.890: Got instructions of length 9
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.890: Received command SLEEP 200
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.890: Processing command SLEEP 200
180s (process:2568): libfprint-virtual_device-DEBUG: 05:03:11.890: Sleeping 200ms
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.091: Sleeping completed
181s (process:2568): libfprint-device-DEBUG: 05:03:12.091: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.091: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.091: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s ok
181s test_list_prints (__main__.VirtualDeviceBusyDeviceOperations.test_list_prints) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.091: 58840467: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.091: 58840491: ../libfprint/drivers/virtual-device-listener.c:153
181s (process:2568): libfprint-device-DEBUG: 05:03:12.091: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.092: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.092: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.092: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.092: Got instructions of length 9
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.092: Received command SLEEP 200
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.092: Processing command SLEEP 200
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.092: Sleeping 200ms
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.292: Sleeping completed
181s (process:2568): libfprint-device-DEBUG: 05:03:12.292: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.292: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.293: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s ok
181s test_open (__main__.VirtualDeviceBusyDeviceOperations.test_open) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.293: 59041870: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.293: 59041893: ../libfprint/drivers/virtual-device-listener.c:153
181s (process:2568): libfprint-device-DEBUG: 05:03:12.293: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.293: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.293: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.293: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.293: Got instructions of length 9
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.293: Received command SLEEP 200
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.293: Processing command SLEEP 200
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.293: Sleeping 200ms
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.293: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.293: Got instructions of length 16
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.293: Received command SET_KEEP_ALIVE 1
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.293: Keep alive toggled: 1
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.493: Sleeping completed
181s (process:2568): libfprint-device-DEBUG: 05:03:12.494: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.494: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.494: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.494: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.494: Got instructions of length 9
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.494: Received command SLEEP 100
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.494: 59243380: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.494: Processing command SLEEP 100
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.494: Sleeping 100ms
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.594: Sleeping completed
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.595: 59343811: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-device-DEBUG: 05:03:12.595: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.595: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.595: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-device-DEBUG: 05:03:12.595: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.595: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.595: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s ok
181s test_verify (__main__.VirtualDeviceBusyDeviceOperations.test_verify) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.595: 59344137: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-device-DEBUG: 05:03:12.595: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.595: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.595: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.595: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.595: Got instructions of length 9
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.595: Received command SLEEP 200
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.595: Processing command SLEEP 200
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.595: Sleeping 200ms
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.796: Sleeping completed
181s (process:2568): libfprint-device-DEBUG: 05:03:12.796: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.796: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.796: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s ok
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.796: 59545535: ../libfprint/drivers/virtual-device.c:752
181s (process:2568): libfprint-context-DEBUG: 05:03:12.797: Initializing FpContext (libfprint version 1.94.9+tod1)
181s (process:2568): libfprint-tod-DEBUG: 05:03:12.797: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
181s (process:2568): libfprint-context-DEBUG: 05:03:12.797: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-f1ifuepz/virtual-device.socket
181s (process:2568): libfprint-context-DEBUG: 05:03:12.797: created
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported probe completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_PROBE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s test_capture (__main__.VirtualDeviceClosed.test_capture) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.798: 59546852: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.798: 59546858: ../libfprint/drivers/virtual-device-listener.c:153
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s ok
181s test_close (__main__.VirtualDeviceClosed.test_close) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.798: 59547039: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.798: 59547042: ../libfprint/drivers/virtual-device-listener.c:153
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s ok
181s test_delete_print (__main__.VirtualDeviceClosed.test_delete_print) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.798: 59547145: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.798: 59547149: ../libfprint/drivers/virtual-device-listener.c:153
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s ok
181s test_enroll (__main__.VirtualDeviceClosed.test_enroll) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.798: 59547259: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.798: 59547262: ../libfprint/drivers/virtual-device-listener.c:153
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s ok
181s test_identify (__main__.VirtualDeviceClosed.test_identify) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.798: 59547361: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.798: 59547364: ../libfprint/drivers/virtual-device-listener.c:153
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s ok
181s test_list_prints (__main__.VirtualDeviceClosed.test_list_prints) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.798: 59547462: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.798: 59547465: ../libfprint/drivers/virtual-device-listener.c:153
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s ok
181s test_verify (__main__.VirtualDeviceClosed.test_verify) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.798: 59547553: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.798: 59547556: ../libfprint/drivers/virtual-device-listener.c:153
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.798: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s ok
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.799: 59547706: ../libfprint/drivers/virtual-device.c:752
181s (process:2568): libfprint-context-DEBUG: 05:03:12.799: Initializing FpContext (libfprint version 1.94.9+tod1)
181s (process:2568): libfprint-tod-DEBUG: 05:03:12.799: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
181s (process:2568): libfprint-context-DEBUG: 05:03:12.799: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-f1ifuepz/virtual-device.socket
181s (process:2568): libfprint-context-DEBUG: 05:03:12.799: created
181s (process:2568): libfprint-context-DEBUG: 05:03:12.799: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-5lp03q24/virtual-device-storage.socket
181s (process:2568): libfprint-context-DEBUG: 05:03:12.799: created
181s (process:2568): libfprint-device-DEBUG: 05:03:12.799: Device reported probe completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.799: Device reported probe completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.799: Completing action FPI_DEVICE_ACTION_PROBE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.799: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-device-DEBUG: 05:03:12.799: Completing action FPI_DEVICE_ACTION_PROBE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.799: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s test_capture_unsupported (__main__.VirtualDeviceStorage.test_capture_unsupported) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.799: 59548563: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.799: 59548583: ../libfprint/drivers/virtual-device-listener.c:153
181s (process:2568): libfprint-device-DEBUG: 05:03:12.799: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.799: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.800: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.800: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.800: Got instructions of length 5
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.800: Received command CONT 
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.800: Processing command CONT 
181s (process:2568): libfprint-device-DEBUG: 05:03:12.800: Device reported deletion completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.800: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.800: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.800: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.800: Got instructions of length 16
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.800: Received command SET_KEEP_ALIVE 0
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.800: Keep alive toggled: 0
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.800: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.800: Got instructions of length 19
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.800: Received command SET_ENROLL_STAGES 5
181s (process:2568): libfprint-device-DEBUG: 05:03:12.800: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.800: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.800: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s ok
181s test_change_enroll_stages (__main__.VirtualDeviceStorage.test_change_enroll_stages) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.800: 59549485: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.800: 59549508: ../libfprint/drivers/virtual-device-listener.c:153
181s (process:2568): libfprint-device-DEBUG: 05:03:12.800: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.800: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.800: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.800: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.800: Got instructions of length 20
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.800: Received command SET_ENROLL_STAGES 20
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.801: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: Got instructions of length 19
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: Received command SET_ENROLL_STAGES 1
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.801: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: Got instructions of length 19
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: Received command SET_ENROLL_STAGES 0
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.801: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: Got instructions of length 5
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: Received command CONT 
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: Processing command CONT 
181s (process:2568): libfprint-device-DEBUG: 05:03:12.801: Device reported deletion completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.801: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.801: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.801: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: Got instructions of length 16
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: Received command SET_KEEP_ALIVE 0
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: Keep alive toggled: 0
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.801: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: Got instructions of length 19
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: Received command SET_ENROLL_STAGES 5
181s (process:2568): libfprint-device-DEBUG: 05:03:12.801: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.801: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.801: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s ok
181s test_change_scan_type (__main__.VirtualDeviceStorage.test_change_scan_type) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: 59550416: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.801: 59550434: ../libfprint/drivers/virtual-device-listener.c:153
181s (process:2568): libfprint-device-DEBUG: 05:03:12.801: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.801: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.801: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.801: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: Got instructions of length 19
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.801: Received command SET_SCAN_TYPE press
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.802: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Got instructions of length 19
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Received command SET_SCAN_TYPE swipe
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.802: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Got instructions of length 25
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Received command SET_SCAN_TYPE eye-contact
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.802: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Got instructions of length 5
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Received command CONT 
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Processing command CONT 
181s (process:2568): libfprint-device-DEBUG: 05:03:12.802: Device reported deletion completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.802: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.802: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.802: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Got instructions of length 16
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Received command SET_KEEP_ALIVE 0
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Keep alive toggled: 0
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.802: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Got instructions of length 19
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Received command SET_ENROLL_STAGES 5
181s (process:2568): libfprint-device-DEBUG: 05:03:12.802: Device reported close completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.802: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.802: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s ok
181s test_clear_storage (__main__.VirtualDeviceStorage.test_clear_storage) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: 59551217: ../libfprint/drivers/virtual-device.c:387
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.802: 59551220: ../libfprint/drivers/virtual-device-listener.c:153
181s (process:2568): libfprint-device-DEBUG: 05:03:12.802: Device reported open completion
181s (process:2568): libfprint-device-DEBUG: 05:03:12.802: Completing action FPI_DEVICE_ACTION_OPEN in idle!
181s (process:2568): libfprint-device-DEBUG: 05:03:12.802: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
181s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:12.802: Got a new connection!
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Got instructions of length 9
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Received command INSERT p1
181s (process:2568): libfprint-virtual_device-DEBUG: 05:03:12.802: Processing command INSERT p1
182s (process:2568): libfprint-device-DEBUG: 05:03:13.303: Device reported listing completion
182s (process:2568): libfprint-device-DEBUG: 05:03:13.303: Completing action FPI_DEVICE_ACTION_LIST in idle!
182s (process:2568): libfprint-device-DEBUG: 05:03:13.303: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
182s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:13.304: Got a new connection!
182s (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.304: Got instructions of length 5
182s (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.304: Received command CONT 
182s (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.304: Processing command CONT 
182s (process:2568): libfprint-device-DEBUG: 05:03:13.304: Device reported deletion completion
182s (process:2568): libfprint-device-DEBUG: 05:03:13.304: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
182s (process:2568): libfprint-device-DEBUG: 05:03:13.304: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
182s (process:2568): libfprint-device-DEBUG: 05:03:13.804: Device reported listing completion
182s (process:2568): libfprint-device-DEBUG: 05:03:13.805: Completing action FPI_DEVICE_ACTION_LIST in idle!
182s (process:2568): libfprint-device-DEBUG: 05:03:13.805: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
182s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:13.805: Got a new connection!
182s (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.805: Got instructions of length 5
182s (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.805: Received command CONT 
182s (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.805: Processing command CONT 
182s (process:2568): libfprint-device-DEBUG: 05:03:13.805: Device reported deletion completion
182s (process:2568): libfprint-device-DEBUG: 05:03:13.805: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
182s (process:2568): libfprint-device-DEBUG: 05:03:13.805: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
182s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:13.805: Got a new connection!
182s (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.805: Got instructions of length 16
182s (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.805: Received command SET_KEEP_ALIVE 0
182s (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.805: Keep alive toggled: 0
182s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:13.805: Got a new connection!
182s (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.805: Got instructions of length 19
182s (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.805: Received command SET_ENROLL_STAGES 5
182s (process:2568): libfprint-device-DEBUG: 05:03:13.805: Device reported close completion
182s (process:2568): libfprint-device-DEBUG: 05:03:13.805: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
182s (process:2568): libfprint-device-DEBUG: 05:03:13.805: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
182s <FPrint.Print object at 0x3ffa26f5700 (FpPrint at 0x355a450)>
182s ok
182s test_clear_storage_error (__main__.VirtualDeviceStorage.test_clear_storage_error) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.805: 60554603: ../libfprint/drivers/virtual-device.c:387
182s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:13.805: 60554610: ../libfprint/drivers/virtual-device-listener.c:153
182s (process:2568): libfprint-device-DEBUG: 05:03:13.806: Device reported open completion
182s (process:2568): libfprint-device-DEBUG: 05:03:13.806: Completing action FPI_DEVICE_ACTION_OPEN in idle!
182s (process:2568): libfprint-device-DEBUG: 05:03:13.806: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
182s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:13.806: Got a new connection!
182s (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.806: Got instructions of length 9
182s (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.806: Received command INSERT p1
182s (process:2568): libfprint-virtual_device-DEBUG: 05:03:13.806: Processing command INSERT p1
183s Executing: libfprint-2/virtual-device.test
183s (process:2568): libfprint-device-DEBUG: 05:03:14.306: Device reported listing completion
183s (process:2568): libfprint-device-DEBUG: 05:03:14.306: Completing action FPI_DEVICE_ACTION_LIST in idle!
183s (process:2568): libfprint-device-DEBUG: 05:03:14.306: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
183s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.307: Got a new connection!
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.307: Got instructions of length 7
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.307: Received command ERROR 5
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.307: Processing command ERROR 5
183s (process:2568): libfprint-device-DEBUG: 05:03:14.307: Device reported deletion completion
183s (process:2568): libfprint-device-DEBUG: 05:03:14.307: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
183s (process:2568): libfprint-device-DEBUG: 05:03:14.307: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
183s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.307: Got a new connection!
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.307: Got instructions of length 5
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.307: Received command CONT 
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.307: Processing command CONT 
183s (process:2568): libfprint-device-DEBUG: 05:03:14.307: Device reported deletion completion
183s (process:2568): libfprint-device-DEBUG: 05:03:14.307: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
183s (process:2568): libfprint-device-DEBUG: 05:03:14.307: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
183s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.307: Got a new connection!
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.307: Got instructions of length 16
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.307: Received command SET_KEEP_ALIVE 0
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.307: Keep alive toggled: 0
183s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.307: Got a new connection!
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.307: Got instructions of length 19
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.307: Received command SET_ENROLL_STAGES 5
183s (process:2568): libfprint-device-DEBUG: 05:03:14.307: Device reported close completion
183s (process:2568): libfprint-device-DEBUG: 05:03:14.307: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
183s (process:2568): libfprint-device-DEBUG: 05:03:14.308: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
183s <FPrint.Print object at 0x3ffa1ec6600 (FpPrint at 0x355bb90)>
183s ok
183s test_close_error (__main__.VirtualDeviceStorage.test_close_error) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.308: 61056784: ../libfprint/drivers/virtual-device.c:387
183s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.308: 61056798: ../libfprint/drivers/virtual-device-listener.c:153
183s (process:2568): libfprint-device-DEBUG: 05:03:14.308: Device reported open completion
183s (process:2568): libfprint-device-DEBUG: 05:03:14.308: Completing action FPI_DEVICE_ACTION_OPEN in idle!
183s (process:2568): libfprint-device-DEBUG: 05:03:14.308: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
183s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.308: Got a new connection!
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.308: Got instructions of length 9
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.308: Received command SLEEP 100
183s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.308: Got a new connection!
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.308: Got instructions of length 7
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.308: Received command ERROR 4
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.308: Processing command SLEEP 100
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.308: Sleeping 100ms
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.408: Sleeping completed
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.408: Processing command ERROR 4
183s (process:2568): libfprint-device-DEBUG: 05:03:14.408: Device reported close completion
183s (process:2568): libfprint-device-DEBUG: 05:03:14.408: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
183s (process:2568): libfprint-device-DEBUG: 05:03:14.408: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
183s ok
183s test_close_while_opening (__main__.VirtualDeviceStorage.test_close_while_opening) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.409: 61157864: ../libfprint/drivers/virtual-device.c:387
183s (process:2568): libfprint-device-DEBUG: 05:03:14.409: Device reported open completion
183s (process:2568): libfprint-device-DEBUG: 05:03:14.409: Completing action FPI_DEVICE_ACTION_OPEN in idle!
183s (process:2568): libfprint-device-DEBUG: 05:03:14.409: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
183s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.409: Got a new connection!
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.409: Got instructions of length 16
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.409: Received command SET_KEEP_ALIVE 1
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.409: Keep alive toggled: 1
183s (process:2568): libfprint-device-DEBUG: 05:03:14.409: Device reported close completion
183s (process:2568): libfprint-device-DEBUG: 05:03:14.409: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
183s (process:2568): libfprint-device-DEBUG: 05:03:14.409: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
183s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.409: Got a new connection!
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.409: Got instructions of length 9
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.409: Received command SLEEP 500
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.409: 61158299: ../libfprint/drivers/virtual-device.c:387
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.409: Processing command SLEEP 500
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.409: Sleeping 500ms
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.910: Sleeping completed
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.910: 61659048: ../libfprint/drivers/virtual-device.c:387
183s (process:2568): libfprint-device-DEBUG: 05:03:14.910: Device reported open completion
183s (process:2568): libfprint-device-DEBUG: 05:03:14.910: Completing action FPI_DEVICE_ACTION_OPEN in idle!
183s (process:2568): libfprint-device-DEBUG: 05:03:14.910: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
183s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.910: Got a new connection!
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.910: Got instructions of length 5
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.910: Received command CONT 
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.910: Processing command CONT 
183s (process:2568): libfprint-device-DEBUG: 05:03:14.910: Device reported deletion completion
183s (process:2568): libfprint-device-DEBUG: 05:03:14.910: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
183s (process:2568): libfprint-device-DEBUG: 05:03:14.910: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
183s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.911: Got a new connection!
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.911: Got instructions of length 16
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.911: Received command SET_KEEP_ALIVE 0
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.911: Keep alive toggled: 0
183s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.911: Got a new connection!
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.911: Got instructions of length 19
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.911: Received command SET_ENROLL_STAGES 5
183s (process:2568): libfprint-device-DEBUG: 05:03:14.911: Device reported close completion
183s (process:2568): libfprint-device-DEBUG: 05:03:14.911: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
183s (process:2568): libfprint-device-DEBUG: 05:03:14.911: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
183s ok
183s test_delayed_open (__main__.VirtualDeviceStorage.test_delayed_open) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.911: 61660074: ../libfprint/drivers/virtual-device.c:387
183s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.911: 61660084: ../libfprint/drivers/virtual-device-listener.c:153
183s (process:2568): libfprint-device-DEBUG: 05:03:14.911: Device reported open completion
183s (process:2568): libfprint-device-DEBUG: 05:03:14.911: Completing action FPI_DEVICE_ACTION_OPEN in idle!
183s (process:2568): libfprint-device-DEBUG: 05:03:14.911: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
183s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.911: Got a new connection!
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.911: Got instructions of length 16
183s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.911: Received command IGNORED_COMMAND 
184s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:14.911: Got a new connection!
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.911: Got instructions of length 9
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.911: Received command SLEEP 500
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.911: Processing command IGNORED_COMMAND 
184s (process:2568): libfprint-device-DEBUG: 05:03:14.911: Device reported close completion
184s (process:2568): libfprint-device-DEBUG: 05:03:14.911: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
184s (process:2568): libfprint-device-DEBUG: 05:03:14.911: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.911: 61660624: ../libfprint/drivers/virtual-device.c:387
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.911: Processing command SLEEP 500
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:14.911: Sleeping 500ms
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.412: Sleeping completed
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.412: 62161344: ../libfprint/drivers/virtual-device.c:387
184s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:15.412: 62161367: ../libfprint/drivers/virtual-device-listener.c:153
184s (process:2568): libfprint-device-DEBUG: 05:03:15.412: Device reported open completion
184s (process:2568): libfprint-device-DEBUG: 05:03:15.413: Completing action FPI_DEVICE_ACTION_OPEN in idle!
184s (process:2568): libfprint-device-DEBUG: 05:03:15.413: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
184s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:15.413: Got a new connection!
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Got instructions of length 5
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Received command CONT 
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Processing command CONT 
184s (process:2568): libfprint-device-DEBUG: 05:03:15.413: Device reported deletion completion
184s (process:2568): libfprint-device-DEBUG: 05:03:15.413: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
184s (process:2568): libfprint-device-DEBUG: 05:03:15.413: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
184s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:15.413: Got a new connection!
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Got instructions of length 16
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Received command SET_KEEP_ALIVE 0
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Keep alive toggled: 0
184s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:15.413: Got a new connection!
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Got instructions of length 19
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Received command SET_ENROLL_STAGES 5
184s (process:2568): libfprint-device-DEBUG: 05:03:15.413: Device reported close completion
184s (process:2568): libfprint-device-DEBUG: 05:03:15.413: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
184s (process:2568): libfprint-device-DEBUG: 05:03:15.413: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
184s ok
184s test_delayed_open_with_keep_alive (__main__.VirtualDeviceStorage.test_delayed_open_with_keep_alive) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: 62162359: ../libfprint/drivers/virtual-device.c:387
184s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:15.413: 62162368: ../libfprint/drivers/virtual-device-listener.c:153
184s (process:2568): libfprint-device-DEBUG: 05:03:15.413: Device reported open completion
184s (process:2568): libfprint-device-DEBUG: 05:03:15.413: Completing action FPI_DEVICE_ACTION_OPEN in idle!
184s (process:2568): libfprint-device-DEBUG: 05:03:15.413: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
184s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:15.413: Got a new connection!
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Got instructions of length 16
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Received command SET_KEEP_ALIVE 1
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Keep alive toggled: 1
184s (process:2568): libfprint-device-DEBUG: 05:03:15.413: Device reported close completion
184s (process:2568): libfprint-device-DEBUG: 05:03:15.413: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
184s (process:2568): libfprint-device-DEBUG: 05:03:15.413: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
184s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:15.413: Got a new connection!
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Got instructions of length 9
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Received command SLEEP 500
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: 62162613: ../libfprint/drivers/virtual-device.c:387
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Processing command SLEEP 500
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.413: Sleeping 500ms
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.914: Sleeping completed
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.914: 62663370: ../libfprint/drivers/virtual-device.c:387
184s (process:2568): libfprint-device-DEBUG: 05:03:15.914: Device reported open completion
184s (process:2568): libfprint-device-DEBUG: 05:03:15.914: Completing action FPI_DEVICE_ACTION_OPEN in idle!
184s (process:2568): libfprint-device-DEBUG: 05:03:15.914: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
184s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:15.915: Got a new connection!
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.915: Got instructions of length 5
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.915: Received command CONT 
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.915: Processing command CONT 
184s (process:2568): libfprint-device-DEBUG: 05:03:15.915: Device reported deletion completion
184s (process:2568): libfprint-device-DEBUG: 05:03:15.915: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
184s (process:2568): libfprint-device-DEBUG: 05:03:15.915: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
184s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:15.915: Got a new connection!
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.915: Got instructions of length 16
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.915: Received command SET_KEEP_ALIVE 0
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.915: Keep alive toggled: 0
184s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:15.915: Got a new connection!
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.915: Got instructions of length 19
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.915: Received command SET_ENROLL_STAGES 5
184s (process:2568): libfprint-device-DEBUG: 05:03:15.915: Device reported close completion
184s (process:2568): libfprint-device-DEBUG: 05:03:15.915: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
184s (process:2568): libfprint-device-DEBUG: 05:03:15.915: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
184s ok
184s test_delete_error (__main__.VirtualDeviceStorage.test_delete_error) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.915: 62664356: ../libfprint/drivers/virtual-device.c:387
184s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:15.915: 62664368: ../libfprint/drivers/virtual-device-listener.c:153
184s (process:2568): libfprint-device-DEBUG: 05:03:15.915: Device reported open completion
184s (process:2568): libfprint-device-DEBUG: 05:03:15.915: Completing action FPI_DEVICE_ACTION_OPEN in idle!
184s (process:2568): libfprint-device-DEBUG: 05:03:15.915: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
184s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:15.915: Got a new connection!
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.915: Got instructions of length 9
184s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.915: Received command SLEEP 100
184s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:15.915: Got a new connection!
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.915: Got instructions of length 7
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.915: Received command ERROR 7
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.916: Processing command SLEEP 100
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:15.916: Sleeping 100ms
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.016: Sleeping completed
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.016: Processing command ERROR 7
185s (process:2568): libfprint-device-DEBUG: 05:03:16.016: Device reported deletion completion
185s (process:2568): libfprint-device-DEBUG: 05:03:16.016: Completing action FPI_DEVICE_ACTION_DELETE in idle!
185s (process:2568): libfprint-device-DEBUG: 05:03:16.016: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
185s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:16.016: Got a new connection!
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.016: Got instructions of length 5
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.016: Received command CONT 
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.016: Processing command CONT 
185s (process:2568): libfprint-device-DEBUG: 05:03:16.016: Device reported deletion completion
185s (process:2568): libfprint-device-DEBUG: 05:03:16.016: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
185s (process:2568): libfprint-device-DEBUG: 05:03:16.016: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
185s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:16.016: Got a new connection!
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Got instructions of length 16
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Received command SET_KEEP_ALIVE 0
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Keep alive toggled: 0
185s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:16.017: Got a new connection!
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Got instructions of length 19
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Received command SET_ENROLL_STAGES 5
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported close completion
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
185s ok
185s test_delete_multiple_times (__main__.VirtualDeviceStorage.test_delete_multiple_times) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: 62765924: ../libfprint/drivers/virtual-device.c:387
185s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:16.017: 62765937: ../libfprint/drivers/virtual-device-listener.c:153
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported open completion
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Completing action FPI_DEVICE_ACTION_OPEN in idle!
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
185s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:16.017: Got a new connection!
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Got instructions of length 16
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Received command SCAN right-thumb
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Processing command SCAN right-thumb
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported enroll progress, reported 1 of 5 have been completed
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Sleeping completed
185s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:16.017: Got a new connection!
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Got instructions of length 16
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Received command SCAN right-thumb
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Processing command SCAN right-thumb
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported enroll progress, reported 2 of 5 have been completed
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Sleeping completed
185s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:16.017: Got a new connection!
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Got instructions of length 16
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Received command SCAN right-thumb
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Processing command SCAN right-thumb
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported enroll progress, reported 3 of 5 have been completed
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Sleeping completed
185s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:16.017: Got a new connection!
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Got instructions of length 16
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Received command SCAN right-thumb
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Processing command SCAN right-thumb
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported finger status change: FP_FINGER_STATUS_NEEDED
185s (process:2568): libfprint-device-DEBUG: 05:03:16.017: Device reported enroll progress, reported 4 of 5 have been completed
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.017: Sleeping completed
185s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:16.018: Got a new connection!
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.018: Got instructions of length 16
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.018: Received command SCAN right-thumb
185s (process:2568): libfprint-virtual_device-DEBUG: 05:03:16.018: Processing command SCAN right-thumb
185s (process:2568): libfprint-device-DEBUG: 05:03:16.018: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
185s (process:2568): libfprint-device-DEBUG: 05:03:16.018: Device reported finger status change: FP_FINGER_STATUS_NEEDED
185s (process:2568): libfprint-device-DEBUG: 05:03:16.018: Device reported enroll progress, reported 5 of 5 have been completed
185s (process:2568): libfprint-device-DEBUG: 05:03:16.018: Device reported enroll completion
185s (process:2568): libfprint-device-DEBUG: 05:03:16.018: Device reported finger status change: FP_FINGER_STATUS_NONE
185s (process:2568): libfprint-device-DEBUG: 05:03:16.018: Print for finger FP_FINGER_RIGHT_THUMB enrolled
185s (process:2568): libfprint-device-DEBUG: 05:03:16.018: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
185s (process:2568): libfprint-device-DEBUG: 05:03:16.018: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
185s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:16.518: Deleting print right-thumb for user testuser
185s (process:2568): libfprint-device-DEBUG: 05:03:16.519: Device reported deletion completion
185s (process:2568): libfprint-device-DEBUG: 05:03:16.519: Completing action FPI_DEVICE_ACTION_DELETE in idle!
185s (process:2568): libfprint-device-DEBUG: 05:03:16.519: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:17.020: Deleting print right-thumb for user testuser
186s (process:2568): libfprint-device-DEBUG: 05:03:17.020: Device reported deletion completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.020: Completing action FPI_DEVICE_ACTION_DELETE in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.020: Updated temperature model after 0.50 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.020: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.020: Got instructions of length 5
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.020: Received command CONT 
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.020: Processing command CONT 
186s (process:2568): libfprint-device-DEBUG: 05:03:17.020: Device reported deletion completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.020: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.020: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.020: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.020: Got instructions of length 16
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.020: Received command SET_KEEP_ALIVE 0
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.020: Keep alive toggled: 0
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.020: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.020: Got instructions of length 19
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.020: Received command SET_ENROLL_STAGES 5
186s (process:2568): libfprint-device-DEBUG: 05:03:17.020: Device reported close completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.020: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.020: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s Enroll done
186s ok
186s test_device_features (__main__.VirtualDeviceStorage.test_device_features) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: 63769708: ../libfprint/drivers/virtual-device.c:387
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.021: 63769718: ../libfprint/drivers/virtual-device-listener.c:153
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Device reported open completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Completing action FPI_DEVICE_ACTION_OPEN in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.021: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Got instructions of length 5
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Received command CONT 
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Processing command CONT 
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Device reported deletion completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.021: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Got instructions of length 16
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Received command SET_KEEP_ALIVE 0
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Keep alive toggled: 0
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.021: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Got instructions of length 19
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Received command SET_ENROLL_STAGES 5
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Device reported close completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s ok
186s test_device_properties (__main__.VirtualDeviceStorage.test_device_properties) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: 63770184: ../libfprint/drivers/virtual-device.c:387
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.021: 63770192: ../libfprint/drivers/virtual-device-listener.c:153
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Device reported open completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Completing action FPI_DEVICE_ACTION_OPEN in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.021: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Got instructions of length 5
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Received command CONT 
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Processing command CONT 
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Device reported deletion completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.021: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Got instructions of length 16
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Received command SET_KEEP_ALIVE 0
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Keep alive toggled: 0
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.021: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Got instructions of length 19
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: Received command SET_ENROLL_STAGES 5
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Device reported close completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s ok
186s test_device_sleep (__main__.VirtualDeviceStorage.test_device_sleep) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.021: 63770569: ../libfprint/drivers/virtual-device.c:387
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.021: 63770577: ../libfprint/drivers/virtual-device-listener.c:153
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Device reported open completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Completing action FPI_DEVICE_ACTION_OPEN in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.021: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.022: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.022: Got instructions of length 10
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.022: Received command SLEEP 1500
186s (process:2568): libfprint-device-DEBUG: 05:03:17.022: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.022: Processing command SLEEP 1500
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.022: Sleeping 1500ms
186s (process:2568): libfprint-device-DEBUG: 05:03:17.322: Idle cancelling on ongoing operation!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.322: Got cancellation!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.322: Device reported finger status change: FP_FINGER_STATUS_NEEDED
186s (process:2568): libfprint-device-DEBUG: 05:03:17.322: Device reported identify completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.322: Device reported finger status change: FP_FINGER_STATUS_NONE
186s (process:2568): libfprint-device-DEBUG: 05:03:17.322: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.322: Updated temperature model after 0.30 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.522: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.522: Got instructions of length 5
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.522: Received command CONT 
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.522: Processing command CONT 
186s (process:2568): libfprint-device-DEBUG: 05:03:17.522: Device reported deletion completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.522: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.522: Updated temperature model after 0.20 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.522: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.522: Got instructions of length 16
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Received command SET_KEEP_ALIVE 0
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Keep alive toggled: 0
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.523: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Got instructions of length 19
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Received command SET_ENROLL_STAGES 5
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Device reported close completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s ok
186s test_device_sleep_before_completing_verify (__main__.VirtualDeviceStorage.test_device_sleep_before_completing_verify) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: 64271937: ../libfprint/drivers/virtual-device.c:387
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.523: 64271950: ../libfprint/drivers/virtual-device-listener.c:153
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Device reported open completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Completing action FPI_DEVICE_ACTION_OPEN in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.523: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Got instructions of length 14
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Received command SCAN foo-print
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Processing command SCAN foo-print
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Device reported finger status change: FP_FINGER_STATUS_NEEDED
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Device reported finger status change: FP_FINGER_STATUS_NEEDED
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Device reported enroll progress, reported 1 of 5 have been completed
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Sleeping completed
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.523: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Got instructions of length 14
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Received command SCAN foo-print
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Processing command SCAN foo-print
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Device reported finger status change: FP_FINGER_STATUS_NEEDED
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Device reported enroll progress, reported 2 of 5 have been completed
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Sleeping completed
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.523: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Got instructions of length 14
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Received command SCAN foo-print
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Processing command SCAN foo-print
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Device reported finger status change: FP_FINGER_STATUS_NEEDED
186s (process:2568): libfprint-device-DEBUG: 05:03:17.523: Device reported enroll progress, reported 3 of 5 have been completed
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Sleeping completed
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.523: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Got instructions of length 14
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Received command SCAN foo-print
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.523: Processing command SCAN foo-print
186s (process:2568): libfprint-device-DEBUG: 05:03:17.524: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
186s (process:2568): libfprint-device-DEBUG: 05:03:17.524: Device reported finger status change: FP_FINGER_STATUS_NEEDED
186s (process:2568): libfprint-device-DEBUG: 05:03:17.524: Device reported enroll progress, reported 4 of 5 have been completed
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.524: Sleeping completed
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.524: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.524: Got instructions of length 14
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.524: Received command SCAN foo-print
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.524: Processing command SCAN foo-print
186s (process:2568): libfprint-device-DEBUG: 05:03:17.524: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
186s (process:2568): libfprint-device-DEBUG: 05:03:17.524: Device reported finger status change: FP_FINGER_STATUS_NEEDED
186s (process:2568): libfprint-device-DEBUG: 05:03:17.524: Device reported enroll progress, reported 5 of 5 have been completed
186s (process:2568): libfprint-device-DEBUG: 05:03:17.524: Device reported enroll completion
186s (process:2568): libfprint-device-DEBUG: 05:03:17.524: Device reported finger status change: FP_FINGER_STATUS_NONE
186s (process:2568): libfprint-device-DEBUG: 05:03:17.524: Print for finger FP_FINGER_LEFT_RING enrolled
186s (process:2568): libfprint-device-DEBUG: 05:03:17.524: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
186s (process:2568): libfprint-device-DEBUG: 05:03:17.524: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.524: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.524: Got instructions of length 9
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.524: Received command SLEEP 100
186s (process:2568): libfprint-device-DEBUG: 05:03:17.524: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.524: Processing command SLEEP 100
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.524: Sleeping 100ms
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.524: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.524: Got instructions of length 14
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.524: Received command SCAN bar-print
186s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:17.524: Got a new connection!
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.524: Got instructions of length 9
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.524: Received command SLEEP 800
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.624: Sleeping completed
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.624: Processing command SCAN bar-print
186s (process:2568): libfprint-device-DEBUG: 05:03:17.624: Device reported finger status change: FP_FINGER_STATUS_NEEDED
186s (process:2568): libfprint-device-DEBUG: 05:03:17.624: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
186s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:17.624: Trying to identify print 'bar-print' against a gallery of 1 prints
186s (process:2568): libfprint-device-DEBUG: 05:03:17.624: Device reported identify result
186s (process:2568): libfprint-device-DEBUG: 05:03:17.624: Device reported finger status change: FP_FINGER_STATUS_NEEDED
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.624: Processing command SLEEP 800
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.624: Sleeping 800ms
186s (process:2568): libfprint-virtual_device-DEBUG: 05:03:17.624: Sleeping now, command queued for later: SCAN bar-print
186s (process:2568): libfprint-device-DEBUG: 05:03:17.861: Updated temperature model after 0.34 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.425: Sleeping completed
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.425: Processing command SCAN bar-print
187s (process:2568): libfprint-device-DEBUG: 05:03:18.425: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
187s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:18.425: Trying to identify print 'bar-print' against a gallery of 1 prints
187s (process:2568): libfprint-device-DEBUG: 05:03:18.425: Device reported finger status change: FP_FINGER_STATUS_NEEDED
187s (process:2568): libfprint-device-DEBUG: 05:03:18.425: Device reported identify completion
187s (process:2568): libfprint-device-DEBUG: 05:03:18.425: Device reported finger status change: FP_FINGER_STATUS_NONE
187s (process:2568): libfprint-device-DEBUG: 05:03:18.425: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
187s (process:2568): libfprint-device-DEBUG: 05:03:18.425: Updated temperature model after 0.56 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
187s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:18.426: Got a new connection!
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Got instructions of length 5
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Received command CONT 
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Processing command CONT 
187s (process:2568): libfprint-device-DEBUG: 05:03:18.426: Device reported deletion completion
187s (process:2568): libfprint-device-DEBUG: 05:03:18.426: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
187s (process:2568): libfprint-device-DEBUG: 05:03:18.426: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
187s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:18.426: Got a new connection!
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Got instructions of length 16
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Received command SET_KEEP_ALIVE 0
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Keep alive toggled: 0
187s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:18.426: Got a new connection!
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Got instructions of length 19
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Received command SET_ENROLL_STAGES 5
187s (process:2568): libfprint-device-DEBUG: 05:03:18.426: Device reported close completion
187s (process:2568): libfprint-device-DEBUG: 05:03:18.426: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
187s (process:2568): libfprint-device-DEBUG: 05:03:18.426: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
187s Enroll done
187s ok
187s test_device_sleep_on_cancellation (__main__.VirtualDeviceStorage.test_device_sleep_on_cancellation) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: 65175143: ../libfprint/drivers/virtual-device.c:387
187s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:18.426: 65175153: ../libfprint/drivers/virtual-device-listener.c:153
187s (process:2568): libfprint-device-DEBUG: 05:03:18.426: Device reported open completion
187s (process:2568): libfprint-device-DEBUG: 05:03:18.426: Completing action FPI_DEVICE_ACTION_OPEN in idle!
187s (process:2568): libfprint-device-DEBUG: 05:03:18.426: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
187s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:18.426: Got a new connection!
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Got instructions of length 26
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Received command SET_CANCELLATION_ENABLED 0
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Cancellation support toggled: 0
187s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:18.426: Got a new connection!
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Got instructions of length 10
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Received command SLEEP 1500
187s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:18.426: Got a new connection!
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Got instructions of length 14
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Received command SCAN foo-print
187s (process:2568): libfprint-device-DEBUG: 05:03:18.426: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Processing command SLEEP 1500
187s (process:2568): libfprint-virtual_device-DEBUG: 05:03:18.426: Sleeping 1500ms
187s (process:2568): libfprint-device-DEBUG: 05:03:18.727: Idle cancelling on ongoing operation!
188s Executing: libfprint-2/virtual-device.test
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.928: Sleeping completed
189s (process:2568): libfprint-device-DEBUG: 05:03:19.928: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.928: Device reported identify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.928: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:19.928: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.928: Updated temperature model after 1.50 seconds, ratio 0.27 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.928: Processing command SCAN foo-print
189s (process:2568): libfprint-device-DEBUG: 05:03:19.928: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.928: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.928: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s ok
189s test_duplicate_enroll (__main__.VirtualDeviceStorage.test_duplicate_enroll) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.928: 66677393: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.928: 66677402: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:19.928: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.928: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.928: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.929: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Received command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported enroll progress, reported 1 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.929: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported enroll progress, reported 2 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.929: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported enroll progress, reported 3 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.929: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported enroll progress, reported 4 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.929: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported enroll progress, reported 5 of 5 have been completed
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Print for finger FP_FINGER_LEFT_LITTLE enrolled
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.929: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Received command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.929: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.929: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.929: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s Enroll done
189s Enroll done
189s ok
189s test_enroll (__main__.VirtualDeviceStorage.test_enroll) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: 66678542: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.929: 66678545: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.929: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.929: Received command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:19.929: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported enroll progress, reported 1 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported enroll progress, reported 2 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported enroll progress, reported 3 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported enroll progress, reported 4 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported enroll progress, reported 5 of 5 have been completed
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Print for finger FP_FINGER_LEFT_LITTLE enrolled
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s Enroll done
189s ok
189s test_enroll_script (__main__.VirtualDeviceStorage.test_enroll_script) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: 66679237: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: 66679240: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.930: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command SET_ENROLL_STAGES 8
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command RETRY 1
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command RETRY 3
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command RETRY 2
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.930: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.930: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.931: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Got instructions of length 8
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Received command SLEEP 10
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.931: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Got instructions of length 8
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Received command SLEEP 20
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.931: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Received command RETRY 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.931: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Received command RETRY 3
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.931: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.931: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Received command SCAN another-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.931: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.931: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Received command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported enroll progress, reported 1 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported enroll progress, reported 2 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Processing command RETRY 1
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported enroll progress, reported 2 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported enroll progress, reported 3 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Processing command RETRY 3
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported enroll progress, reported 3 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported enroll progress, reported 4 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Processing command RETRY 2
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported enroll progress, reported 4 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.931: Device reported enroll progress, reported 5 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Processing command SLEEP 10
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.931: Sleeping 10ms
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.941: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.941: Processing command SLEEP 20
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.941: Sleeping 20ms
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.961: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Processing command RETRY 0
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported enroll progress, reported 5 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Processing command RETRY 3
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported enroll progress, reported 5 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported enroll progress, reported 6 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Processing command SCAN another-id
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported enroll progress, reported 6 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported enroll progress, reported 7 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported enroll progress, reported 8 of 8 have been completed
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Print for finger FP_FINGER_UNKNOWN enrolled
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.962: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.962: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.962: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s ok
189s test_enroll_script_interactive (__main__.VirtualDeviceStorage.test_enroll_script_interactive) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: 66711381: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.962: 66711391: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:19.962: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.962: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Got instructions of length 8
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Received command SLEEP 50
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.962: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.962: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.962: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.963: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Received command RETRY 1
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.963: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.963: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Got instructions of length 8
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Received command SLEEP 50
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.963: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.963: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Received command RETRY 2
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.963: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Received command SCAN another-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:19.963: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Received command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:19.963: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Processing command SLEEP 50
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:19.963: Sleeping 50ms
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.013: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.013: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.013: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.013: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.013: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.013: Device reported enroll progress, reported 1 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.013: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.013: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.013: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.013: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.013: Device reported enroll progress, reported 2 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.013: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.013: Processing command RETRY 1
189s (process:2568): libfprint-device-DEBUG: 05:03:20.013: Device reported enroll progress, reported 2 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.013: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.013: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.013: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.013: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.013: Device reported enroll progress, reported 3 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.013: Processing command SLEEP 50
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.013: Sleeping 50ms
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Device reported enroll progress, reported 4 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Processing command RETRY 2
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Device reported enroll progress, reported 4 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Processing command SCAN another-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Device reported enroll progress, reported 4 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Device reported enroll progress, reported 5 of 5 have been completed
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Print for finger FP_FINGER_UNKNOWN enrolled
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.064: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.064: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.064: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.064: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.064: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s ok
189s test_enroll_verify_error (__main__.VirtualDeviceStorage.test_enroll_verify_error) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: 66813664: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.065: 66813677: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.065: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Received command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported enroll progress, reported 1 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.065: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported enroll progress, reported 2 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.065: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported enroll progress, reported 3 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.065: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported enroll progress, reported 4 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.065: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported enroll progress, reported 5 of 5 have been completed
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Print for finger FP_FINGER_LEFT_RING enrolled
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.065: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Received command ERROR 0
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.065: Processing command ERROR 0
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported identify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.065: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.066: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.066: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.066: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s Enroll done
189s ok
189s test_enroll_verify_match (__main__.VirtualDeviceStorage.test_enroll_verify_match) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: 66814968: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.066: 66814976: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.066: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Received command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported enroll progress, reported 1 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.066: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported enroll progress, reported 2 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.066: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported enroll progress, reported 3 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.066: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported enroll progress, reported 4 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.066: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.066: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported enroll progress, reported 5 of 5 have been completed
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Print for finger FP_FINGER_LEFT_THUMB enrolled
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.066: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.067: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Received command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:20.067: Trying to identify print 'testprint' against a gallery of 1 prints
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported identify result
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported identify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.067: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.067: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.067: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s Enroll done
189s ok
189s test_enroll_verify_no_match (__main__.VirtualDeviceStorage.test_enroll_verify_no_match) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: 66816158: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.067: 66816165: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.067: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Received command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported enroll progress, reported 1 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.067: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported enroll progress, reported 2 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.067: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported enroll progress, reported 3 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.067: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.067: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.067: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported enroll progress, reported 4 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.068: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported enroll progress, reported 5 of 5 have been completed
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Print for finger FP_FINGER_LEFT_RING enrolled
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.068: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Got instructions of length 18
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Received command SCAN not-testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Processing command SCAN not-testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:20.068: Trying to identify print 'not-testprint' against a gallery of 1 prints
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported identify result
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported identify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.068: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.068: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.068: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s Enroll done
189s ok
189s test_enroll_verify_retry (__main__.VirtualDeviceStorage.test_enroll_verify_retry) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: 66817323: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.068: 66817330: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.068: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Received command RETRY 1
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Processing command RETRY 1
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Virtual device scan failed with error: The swipe was too short, please try again.
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported verify result
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported verify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.068: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.068: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.068: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.069: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:20.069: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.069: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.069: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s ok
189s test_enroll_verify_script (__main__.VirtualDeviceStorage.test_enroll_verify_script) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: 66817860: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: 66817869: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:20.069: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.069: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.069: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Received command SET_ENROLL_STAGES 8
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Received command RETRY 1
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Received command RETRY 3
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Received command RETRY 2
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 8
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Received command SLEEP 10
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 8
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Received command SLEEP 20
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Received command RETRY 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.069: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.069: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Received command RETRY 3
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.070: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.070: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Received command SCAN another-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.070: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Received command SCAN print-id
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.070: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Received command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported enroll progress, reported 1 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported enroll progress, reported 2 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Processing command RETRY 1
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported enroll progress, reported 2 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported enroll progress, reported 3 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Processing command RETRY 3
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported enroll progress, reported 3 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported enroll progress, reported 4 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Processing command RETRY 2
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported enroll progress, reported 4 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.070: Device reported enroll progress, reported 5 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Processing command SLEEP 10
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.070: Sleeping 10ms
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.080: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.080: Processing command SLEEP 20
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.080: Sleeping 20ms
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.100: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.100: Processing command RETRY 0
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Device reported enroll progress, reported 5 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.100: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.100: Processing command RETRY 3
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Device reported enroll progress, reported 5 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.100: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.100: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Device reported enroll progress, reported 6 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.100: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.100: Processing command SCAN another-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Device reported enroll progress, reported 6 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.100: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.100: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Device reported enroll progress, reported 7 of 8 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.100: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.100: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Device reported enroll progress, reported 8 of 8 have been completed
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Print for finger FP_FINGER_UNKNOWN enrolled
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.100: Updated temperature model after 0.03 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.100: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.100: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.101: Received command RETRY 2
189s (process:2568): libfprint-device-DEBUG: 05:03:20.101: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.101: Processing command RETRY 2
189s (process:2568): libfprint-device-DEBUG: 05:03:20.101: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.101: Virtual device scan failed with error: The finger was not centered properly, please try again.
189s (process:2568): libfprint-device-DEBUG: 05:03:20.101: Device reported verify result
189s (process:2568): libfprint-device-DEBUG: 05:03:20.101: Device reported verify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.101: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.101: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.101: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.101: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.101: Got instructions of length 8
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.101: Received command SLEEP 50
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.101: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.101: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.101: Received command RETRY 1
189s (process:2568): libfprint-device-DEBUG: 05:03:20.101: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.101: Processing command SLEEP 50
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.101: Sleeping 50ms
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.151: Sleeping completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.151: Processing command RETRY 1
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.151: Virtual device scan failed with error: The swipe was too short, please try again.
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Device reported verify result
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Device reported verify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Updated temperature model after 0.05 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.151: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.151: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.151: Received command SCAN another-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.151: Processing command SCAN another-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.151: Virtual device scanned print another-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Device reported verify result
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Device reported verify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.151: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.151: Got instructions of length 13
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.151: Received command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.151: Processing command SCAN print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.151: Virtual device scanned print print-id
189s (process:2568): libfprint-device-DEBUG: 05:03:20.151: Device reported verify result
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Device reported verify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.152: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.152: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.152: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s ok
189s test_enroll_with_retry (__main__.VirtualDeviceStorage.test_enroll_with_retry) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: 66901076: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.152: 66901090: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.152: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Received command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Device reported enroll progress, reported 1 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.152: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Device reported enroll progress, reported 2 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.152: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Received command RETRY 1
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Processing command RETRY 1
189s (process:2568): libfprint-device-DEBUG: 05:03:20.152: Device reported enroll progress, reported 2 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.152: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.152: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported enroll progress, reported 3 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.153: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported enroll progress, reported 4 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.153: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported enroll progress, reported 5 of 5 have been completed
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Print for finger FP_FINGER_LEFT_LITTLE enrolled
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.153: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.153: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.153: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s Enroll done
189s ok
189s test_finger_status (__main__.VirtualDeviceStorage.test_finger_status) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: 66902296: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.153: 66902305: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.153: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Got instructions of length 8
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Received command FINGER 1
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Processing command FINGER 1
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.153: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Got instructions of length 8
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Received command FINGER 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Processing command FINGER 0
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Idle cancelling on ongoing operation!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.153: Got cancellation!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported identify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.153: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.154: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.154: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.154: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.154: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:20.154: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.154: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.154: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.154: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.154: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.154: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.154: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.154: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.154: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.154: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:20.154: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.154: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.154: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s ok
189s test_finger_status_after_sleep (__main__.VirtualDeviceStorage.test_finger_status_after_sleep) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.154: 66902936: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.154: 66902943: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:20.154: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.154: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.154: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.154: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.154: Got instructions of length 8
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.154: Received command SLEEP 10
189s (process:2568): libfprint-device-DEBUG: 05:03:20.154: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.154: Processing command SLEEP 10
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.154: Sleeping 10ms
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.164: Sleeping completed
189s (process:2568): libfprint-device-DEBUG: 05:03:20.164: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.164: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.164: Got instructions of length 8
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.164: Received command FINGER 1
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.164: Processing command FINGER 1
189s (process:2568): libfprint-device-DEBUG: 05:03:20.164: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.164: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.164: Got instructions of length 8
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.164: Received command FINGER 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.164: Processing command FINGER 0
189s (process:2568): libfprint-device-DEBUG: 05:03:20.164: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.164: Idle cancelling on ongoing operation!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.164: Got cancellation!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.164: Device reported identify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.164: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.164: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.164: Updated temperature model after 0.01 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.164: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.164: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.164: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.164: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:20.164: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.164: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.164: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.164: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.165: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s ok
189s test_identify_match (__main__.VirtualDeviceStorage.test_identify_match) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: 66913827: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.165: 66913837: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.165: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Received command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Processing command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported enroll progress, reported 1 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.165: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Received command SCAN right-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Processing command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported enroll progress, reported 2 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.165: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Received command SCAN right-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Processing command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported enroll progress, reported 3 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.165: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Received command SCAN right-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Processing command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported enroll progress, reported 4 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.165: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Received command SCAN right-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Processing command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported enroll progress, reported 5 of 5 have been completed
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Print for finger FP_FINGER_RIGHT_THUMB enrolled
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.165: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Received command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.165: Processing command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported enroll progress, reported 1 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.166: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Received command SCAN left-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Processing command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported enroll progress, reported 2 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.166: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Received command SCAN left-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Processing command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported enroll progress, reported 3 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.166: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Received command SCAN left-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Processing command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported enroll progress, reported 4 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.166: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Received command SCAN left-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Processing command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported enroll progress, reported 5 of 5 have been completed
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Print for finger FP_FINGER_LEFT_THUMB enrolled
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.166: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Received command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Processing command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:20.166: Trying to identify print 'right-thumb' against a gallery of 2 prints
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported identify result
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported identify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.166: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Received command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Processing command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:20.166: Trying to identify print 'left-thumb' against a gallery of 2 prints
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported identify result
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported identify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.166: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.166: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.166: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.166: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.167: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s Enroll done
189s Enroll done
189s ok
189s test_identify_missing_print (__main__.VirtualDeviceStorage.test_identify_missing_print) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: 66915813: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.167: 66915821: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.167: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Got instructions of length 23
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Received command SCAN not-existing-print
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Processing command SCAN not-existing-print
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:20.167: Trying to identify print 'not-existing-print' against a gallery of 1 prints
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported identify result
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported identify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.167: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.167: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.167: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s ok
189s test_identify_no_match (__main__.VirtualDeviceStorage.test_identify_no_match) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: 66916349: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.167: 66916355: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.167: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Received command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Processing command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported enroll progress, reported 1 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.167: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Received command SCAN right-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Processing command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.167: Device reported enroll progress, reported 2 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.167: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.168: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Received command SCAN right-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Processing command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported enroll progress, reported 3 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.168: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Received command SCAN right-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Processing command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported enroll progress, reported 4 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.168: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Received command SCAN right-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Processing command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported enroll progress, reported 5 of 5 have been completed
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Print for finger FP_FINGER_RIGHT_THUMB enrolled
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.168: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Received command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Processing command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported enroll progress, reported 1 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.168: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Received command SCAN left-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Processing command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported enroll progress, reported 2 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.168: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Received command SCAN left-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Processing command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported enroll progress, reported 3 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.168: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Received command SCAN left-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Processing command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported enroll progress, reported 4 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.168: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Received command SCAN left-thumb
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.168: Processing command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported enroll progress, reported 5 of 5 have been completed
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Print for finger FP_FINGER_LEFT_THUMB enrolled
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.168: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.169: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Received command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Processing command SCAN right-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:20.169: Trying to identify print 'right-thumb' against a gallery of 1 prints
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported identify result
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported identify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.169: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Got instructions of length 15
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Received command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Processing command SCAN left-thumb
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:20.169: Trying to identify print 'left-thumb' against a gallery of 1 prints
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported identify result
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported identify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.169: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.169: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.169: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s Enroll done
189s Enroll done
189s ok
189s test_identify_retry (__main__.VirtualDeviceStorage.test_identify_retry) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: 66918288: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.169: 66918295: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.169: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Got instructions of length 7
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Received command RETRY 1
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Processing command RETRY 1
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported identify result
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported identify completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.169: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.169: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.169: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.169: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.169: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s ok
189s test_identify_unsupported (__main__.VirtualDeviceStorage.test_identify_unsupported) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: 66918726: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.170: 66918729: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s skipped 'Device supports identification'
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.170: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Got instructions of length 5
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Received command CONT 
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Processing command CONT 
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported deletion completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.170: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Got instructions of length 16
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Received command SET_KEEP_ALIVE 0
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Keep alive toggled: 0
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.170: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Got instructions of length 19
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Received command SET_ENROLL_STAGES 5
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported close completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s test_list_delete (__main__.VirtualDeviceStorage.test_list_delete) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: 66918996: ../libfprint/drivers/virtual-device.c:387
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.170: 66918999: ../libfprint/drivers/virtual-device-listener.c:153
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported open completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Completing action FPI_DEVICE_ACTION_OPEN in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.170: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Received command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported enroll progress, reported 1 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.170: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported enroll progress, reported 2 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.170: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported enroll progress, reported 3 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.170: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported enroll progress, reported 4 of 5 have been completed
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Sleeping completed
189s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:20.170: Got a new connection!
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Got instructions of length 14
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Received command SCAN testprint
189s (process:2568): libfprint-virtual_device-DEBUG: 05:03:20.170: Processing command SCAN testprint
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported finger status change: FP_FINGER_STATUS_NEEDED
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported enroll progress, reported 5 of 5 have been completed
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported enroll completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Device reported finger status change: FP_FINGER_STATUS_NONE
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Print for finger FP_FINGER_RIGHT_THUMB enrolled
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.170: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
189s (process:2568): libfprint-device-DEBUG: 05:03:20.671: Device reported listing completion
189s (process:2568): libfprint-device-DEBUG: 05:03:20.671: Completing action FPI_DEVICE_ACTION_LIST in idle!
189s (process:2568): libfprint-device-DEBUG: 05:03:20.671: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
190s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:21.172: Deleting print testprint for user testuser
190s (process:2568): libfprint-device-DEBUG: 05:03:21.172: Device reported deletion completion
190s (process:2568): libfprint-device-DEBUG: 05:03:21.172: Completing action FPI_DEVICE_ACTION_DELETE in idle!
190s (process:2568): libfprint-device-DEBUG: 05:03:21.172: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
190s (process:2568): libfprint-device-DEBUG: 05:03:21.673: Device reported listing completion
190s (process:2568): libfprint-device-DEBUG: 05:03:21.673: Completing action FPI_DEVICE_ACTION_LIST in idle!
190s (process:2568): libfprint-device-DEBUG: 05:03:21.673: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
190s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:21.674: Got a new connection!
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Got instructions of length 5
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Received command CONT 
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Processing command CONT 
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Device reported deletion completion
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
190s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:21.674: Got a new connection!
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Got instructions of length 16
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Received command SET_KEEP_ALIVE 0
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Keep alive toggled: 0
190s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:21.674: Got a new connection!
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Got instructions of length 19
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Received command SET_ENROLL_STAGES 5
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Device reported close completion
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
190s Enroll done
190s <FPrint.Print object at 0x3ffa1ed33c0 (FpPrint at 0x35623a0)>
190s blub 'testprint' <class 'gi.overrides.GLib.Variant'>
190s ok
190s test_list_delete_missing (__main__.VirtualDeviceStorage.test_list_delete_missing) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: 68423227: ../libfprint/drivers/virtual-device.c:387
190s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:21.674: 68423240: ../libfprint/drivers/virtual-device-listener.c:153
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Device reported open completion
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Completing action FPI_DEVICE_ACTION_OPEN in idle!
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
190s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:21.674: Got a new connection!
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Got instructions of length 14
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Received command SCAN testprint
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Processing command SCAN testprint
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Device reported finger status change: FP_FINGER_STATUS_NEEDED
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Device reported finger status change: FP_FINGER_STATUS_NEEDED
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Device reported enroll progress, reported 1 of 5 have been completed
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Sleeping completed
190s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:21.674: Got a new connection!
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Got instructions of length 14
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Received command SCAN testprint
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.674: Processing command SCAN testprint
190s (process:2568): libfprint-device-DEBUG: 05:03:21.674: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Device reported finger status change: FP_FINGER_STATUS_NEEDED
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Device reported enroll progress, reported 2 of 5 have been completed
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Sleeping completed
190s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:21.675: Got a new connection!
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Got instructions of length 14
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Received command SCAN testprint
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Processing command SCAN testprint
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Device reported finger status change: FP_FINGER_STATUS_NEEDED
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Device reported enroll progress, reported 3 of 5 have been completed
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Sleeping completed
190s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:21.675: Got a new connection!
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Got instructions of length 14
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Received command SCAN testprint
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Processing command SCAN testprint
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Device reported finger status change: FP_FINGER_STATUS_NEEDED
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Device reported enroll progress, reported 4 of 5 have been completed
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Sleeping completed
190s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:21.675: Got a new connection!
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Got instructions of length 14
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Received command SCAN testprint
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Processing command SCAN testprint
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Device reported finger status change: FP_FINGER_STATUS_NEEDED
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Device reported enroll progress, reported 5 of 5 have been completed
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Device reported enroll completion
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Device reported finger status change: FP_FINGER_STATUS_NONE
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Print for finger FP_FINGER_RIGHT_THUMB enrolled
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
190s (process:2568): libfprint-device-DEBUG: 05:03:21.675: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
190s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:21.675: Got a new connection!
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Got instructions of length 16
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Received command REMOVE testprint
190s (process:2568): libfprint-virtual_device-DEBUG: 05:03:21.675: Processing command REMOVE testprint
191s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:22.176: Deleting print testprint for user testuser
191s (process:2568): libfprint-device-DEBUG: 05:03:22.176: Device reported deletion completion
191s (process:2568): libfprint-device-DEBUG: 05:03:22.176: Completing action FPI_DEVICE_ACTION_DELETE in idle!
191s (process:2568): libfprint-device-DEBUG: 05:03:22.176: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.176: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.176: Got instructions of length 5
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.176: Received command CONT 
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.176: Processing command CONT 
191s (process:2568): libfprint-device-DEBUG: 05:03:22.176: Device reported deletion completion
191s (process:2568): libfprint-device-DEBUG: 05:03:22.176: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
191s (process:2568): libfprint-device-DEBUG: 05:03:22.176: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.177: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.177: Got instructions of length 16
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.177: Received command SET_KEEP_ALIVE 0
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.177: Keep alive toggled: 0
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.177: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.177: Got instructions of length 19
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.177: Received command SET_ENROLL_STAGES 5
191s (process:2568): libfprint-device-DEBUG: 05:03:22.177: Device reported close completion
191s (process:2568): libfprint-device-DEBUG: 05:03:22.177: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
191s (process:2568): libfprint-device-DEBUG: 05:03:22.177: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
191s Enroll done
191s ok
191s test_list_empty (__main__.VirtualDeviceStorage.test_list_empty) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.177: 68925960: ../libfprint/drivers/virtual-device.c:387
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.177: 68925972: ../libfprint/drivers/virtual-device-listener.c:153
191s (process:2568): libfprint-device-DEBUG: 05:03:22.177: Device reported open completion
191s (process:2568): libfprint-device-DEBUG: 05:03:22.177: Completing action FPI_DEVICE_ACTION_OPEN in idle!
191s (process:2568): libfprint-device-DEBUG: 05:03:22.177: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
191s (process:2568): libfprint-device-DEBUG: 05:03:22.678: Device reported listing completion
191s (process:2568): libfprint-device-DEBUG: 05:03:22.678: Completing action FPI_DEVICE_ACTION_LIST in idle!
191s (process:2568): libfprint-device-DEBUG: 05:03:22.678: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.678: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.678: Got instructions of length 5
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.678: Received command CONT 
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.678: Processing command CONT 
191s (process:2568): libfprint-device-DEBUG: 05:03:22.678: Device reported deletion completion
191s (process:2568): libfprint-device-DEBUG: 05:03:22.678: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
191s (process:2568): libfprint-device-DEBUG: 05:03:22.678: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.678: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.678: Got instructions of length 16
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.678: Received command SET_KEEP_ALIVE 0
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.678: Keep alive toggled: 0
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.678: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.678: Got instructions of length 19
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.678: Received command SET_ENROLL_STAGES 5
191s (process:2568): libfprint-device-DEBUG: 05:03:22.679: Device reported close completion
191s (process:2568): libfprint-device-DEBUG: 05:03:22.679: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
191s (process:2568): libfprint-device-DEBUG: 05:03:22.679: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
191s ok
191s test_list_error (__main__.VirtualDeviceStorage.test_list_error) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.679: 69427845: ../libfprint/drivers/virtual-device.c:387
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.679: 69427880: ../libfprint/drivers/virtual-device-listener.c:153
191s (process:2568): libfprint-device-DEBUG: 05:03:22.679: Device reported open completion
191s (process:2568): libfprint-device-DEBUG: 05:03:22.679: Completing action FPI_DEVICE_ACTION_OPEN in idle!
191s (process:2568): libfprint-device-DEBUG: 05:03:22.679: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.679: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.679: Got instructions of length 9
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.679: Received command SLEEP 100
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.679: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.679: Got instructions of length 7
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.679: Received command ERROR 4
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.679: Processing command SLEEP 100
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.679: Sleeping 100ms
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.779: Sleeping completed
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.779: Processing command ERROR 4
191s (process:2568): libfprint-device-DEBUG: 05:03:22.779: Device reported listing completion
191s (process:2568): libfprint-device-DEBUG: 05:03:22.780: Completing action FPI_DEVICE_ACTION_LIST in idle!
191s (process:2568): libfprint-device-DEBUG: 05:03:22.780: Updated temperature model after 0.10 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.780: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.780: Got instructions of length 5
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.780: Received command CONT 
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.780: Processing command CONT 
191s (process:2568): libfprint-device-DEBUG: 05:03:22.780: Device reported deletion completion
191s (process:2568): libfprint-device-DEBUG: 05:03:22.780: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
191s (process:2568): libfprint-device-DEBUG: 05:03:22.780: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.780: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.780: Got instructions of length 16
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.780: Received command SET_KEEP_ALIVE 0
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.780: Keep alive toggled: 0
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.780: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.780: Got instructions of length 19
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.780: Received command SET_ENROLL_STAGES 5
191s (process:2568): libfprint-device-DEBUG: 05:03:22.780: Device reported close completion
191s (process:2568): libfprint-device-DEBUG: 05:03:22.780: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
191s (process:2568): libfprint-device-DEBUG: 05:03:22.780: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
191s ok
191s test_list_populated (__main__.VirtualDeviceStorage.test_list_populated) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.780: 69529611: ../libfprint/drivers/virtual-device.c:387
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.780: 69529620: ../libfprint/drivers/virtual-device-listener.c:153
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported open completion
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Completing action FPI_DEVICE_ACTION_OPEN in idle!
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.781: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Got instructions of length 9
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Received command INSERT p1
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.781: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Got instructions of length 7
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Received command SCAN p2
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Processing command INSERT p1
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Processing command SCAN p2
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported enroll progress, reported 1 of 5 have been completed
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Sleeping completed
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.781: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Got instructions of length 7
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Received command SCAN p2
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Processing command SCAN p2
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported enroll progress, reported 2 of 5 have been completed
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Sleeping completed
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.781: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Got instructions of length 7
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Received command SCAN p2
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Processing command SCAN p2
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported enroll progress, reported 3 of 5 have been completed
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Sleeping completed
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.781: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Got instructions of length 7
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Received command SCAN p2
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Processing command SCAN p2
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported enroll progress, reported 4 of 5 have been completed
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Sleeping completed
191s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:22.781: Got a new connection!
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Got instructions of length 7
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Received command SCAN p2
191s (process:2568): libfprint-virtual_device-DEBUG: 05:03:22.781: Processing command SCAN p2
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported finger status change: FP_FINGER_STATUS_NEEDED
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported enroll progress, reported 5 of 5 have been completed
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported enroll completion
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Device reported finger status change: FP_FINGER_STATUS_NONE
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Print for finger FP_FINGER_LEFT_LITTLE enrolled
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
191s (process:2568): libfprint-device-DEBUG: 05:03:22.781: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-device-DEBUG: 05:03:23.282: Device reported listing completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.282: Completing action FPI_DEVICE_ACTION_LIST in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.282: Updated temperature model after 0.50 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.283: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: Got instructions of length 5
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: Received command CONT 
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: Processing command CONT 
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Device reported deletion completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.283: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: Got instructions of length 16
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: Received command SET_KEEP_ALIVE 0
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: Keep alive toggled: 0
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.283: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: Got instructions of length 19
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: Received command SET_ENROLL_STAGES 5
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Device reported close completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s Enroll done
192s ok
192s test_open_error (__main__.VirtualDeviceStorage.test_open_error) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: 70032227: ../libfprint/drivers/virtual-device.c:387
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.283: 70032233: ../libfprint/drivers/virtual-device-listener.c:153
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Device reported open completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Completing action FPI_DEVICE_ACTION_OPEN in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.283: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: Got instructions of length 16
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: Received command IGNORED_COMMAND 
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.283: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: Got instructions of length 7
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: Received command ERROR 5
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: Processing command IGNORED_COMMAND 
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Device reported close completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: 70032618: ../libfprint/drivers/virtual-device.c:387
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.283: Processing command ERROR 5
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Device reported open completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Completing action FPI_DEVICE_ACTION_OPEN in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.283: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s ok
192s test_open_error_with_keep_alive (__main__.VirtualDeviceStorage.test_open_error_with_keep_alive) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: 70032686: ../libfprint/drivers/virtual-device.c:387
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.284: 70032689: ../libfprint/drivers/virtual-device-listener.c:153
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported open completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Completing action FPI_DEVICE_ACTION_OPEN in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.284: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Got instructions of length 16
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Received command SET_KEEP_ALIVE 1
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Keep alive toggled: 1
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported close completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.284: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Got instructions of length 7
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Received command ERROR 5
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: 70032849: ../libfprint/drivers/virtual-device.c:387
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Processing command ERROR 5
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported open completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Completing action FPI_DEVICE_ACTION_OPEN in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s ok
192s test_quick_enroll (__main__.VirtualDeviceStorage.test_quick_enroll) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: 70032894: ../libfprint/drivers/virtual-device.c:387
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported open completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Completing action FPI_DEVICE_ACTION_OPEN in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.284: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Got instructions of length 19
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Received command SET_ENROLL_STAGES 1
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.284: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Got instructions of length 14
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Received command SCAN testprint
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Processing command SCAN testprint
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported finger status change: FP_FINGER_STATUS_NEEDED
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported finger status change: FP_FINGER_STATUS_NEEDED
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported enroll progress, reported 1 of 1 have been completed
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported enroll completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported finger status change: FP_FINGER_STATUS_NONE
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Print for finger FP_FINGER_LEFT_LITTLE enrolled
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.284: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Got instructions of length 5
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Received command CONT 
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Processing command CONT 
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported deletion completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.284: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Got instructions of length 16
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Received command SET_KEEP_ALIVE 0
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Keep alive toggled: 0
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.284: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Got instructions of length 19
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Received command SET_ENROLL_STAGES 5
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported close completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s Enroll done
192s ok
192s test_verify_missing_print (__main__.VirtualDeviceStorage.test_verify_missing_print) ... (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: 70033379: ../libfprint/drivers/virtual-device.c:387
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.284: 70033382: ../libfprint/drivers/virtual-device-listener.c:153
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported open completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Completing action FPI_DEVICE_ACTION_OPEN in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.284: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Got instructions of length 23
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Received command SCAN not-existing-print
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Processing command SCAN not-existing-print
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported finger status change: FP_FINGER_STATUS_NEEDED
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Virtual device scanned print not-existing-print
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported verify result
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported finger status change: FP_FINGER_STATUS_NEEDED
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported verify completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported finger status change: FP_FINGER_STATUS_NONE
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.284: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Got instructions of length 5
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Received command CONT 
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Processing command CONT 
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Device reported deletion completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.284: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.284: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Got instructions of length 16
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Received command SET_KEEP_ALIVE 0
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.284: Keep alive toggled: 0
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.285: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.285: Got instructions of length 19
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.285: Received command SET_ENROLL_STAGES 5
192s (process:2568): libfprint-device-DEBUG: 05:03:23.285: Device reported close completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.285: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.285: Updated temperature model after 0.00 seconds, ratio 0.28 -> 0.28, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s ok
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.285: 70033892: ../libfprint/drivers/virtual-device.c:752
192s test_device_unplug (__main__.VirtualDeviceUnplugging.test_device_unplug) ... (process:2568): libfprint-context-DEBUG: 05:03:23.285: Initializing FpContext (libfprint version 1.94.9+tod1)
192s (process:2568): libfprint-tod-DEBUG: 05:03:23.285: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
192s (process:2568): libfprint-context-DEBUG: 05:03:23.285: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-egmrnjrv/virtual-device.socket
192s (process:2568): libfprint-context-DEBUG: 05:03:23.285: created
192s (process:2568): libfprint-context-DEBUG: 05:03:23.286: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-5lp03q24/virtual-device-storage.socket
192s (process:2568): libfprint-context-DEBUG: 05:03:23.286: created
192s (process:2568): libfprint-device-DEBUG: 05:03:23.286: Device reported probe completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.286: Device reported probe completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.286: Completing action FPI_DEVICE_ACTION_PROBE in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.286: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
192s (process:2568): libfprint-device-DEBUG: 05:03:23.286: Completing action FPI_DEVICE_ACTION_PROBE in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.286: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.286: 70034892: ../libfprint/drivers/virtual-device.c:387
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.286: 70034909: ../libfprint/drivers/virtual-device-listener.c:153
192s (process:2568): libfprint-device-DEBUG: 05:03:23.286: Device reported open completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.286: Completing action FPI_DEVICE_ACTION_OPEN in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.286: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.286: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.286: Got instructions of length 7
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.286: Received command UNPLUG 
192s (process:2568): libfprint-device-DEBUG: 05:03:23.286: Device reported close completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.286: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.286: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.286: 70035411: ../libfprint/drivers/virtual-device.c:752
192s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:23.286: 70035429: ../libfprint/drivers/virtual-device-storage.c:253
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.286: 70035444: ../libfprint/drivers/virtual-device.c:752
192s ok
192s test_device_unplug_during_verify (__main__.VirtualDeviceUnplugging.test_device_unplug_during_verify) ... (process:2568): libfprint-context-DEBUG: 05:03:23.286: Initializing FpContext (libfprint version 1.94.9+tod1)
192s (process:2568): libfprint-tod-DEBUG: 05:03:23.286: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
192s (process:2568): libfprint-context-DEBUG: 05:03:23.287: Found virtual environment device: FP_VIRTUAL_DEVICE, /tmp/libfprint-egmrnjrv/virtual-device.socket
192s (process:2568): libfprint-context-DEBUG: 05:03:23.287: created
192s (process:2568): libfprint-context-DEBUG: 05:03:23.287: Found virtual environment device: FP_VIRTUAL_DEVICE_STORAGE, /tmp/libfprint-5lp03q24/virtual-device-storage.socket
192s (process:2568): libfprint-context-DEBUG: 05:03:23.287: created
192s (process:2568): libfprint-device-DEBUG: 05:03:23.287: Device reported probe completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.287: Device reported probe completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.287: Completing action FPI_DEVICE_ACTION_PROBE in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.287: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
192s (process:2568): libfprint-device-DEBUG: 05:03:23.287: Completing action FPI_DEVICE_ACTION_PROBE in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.287: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.287: 70035904: ../libfprint/drivers/virtual-device.c:387
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.287: 70035917: ../libfprint/drivers/virtual-device-listener.c:153
192s (process:2568): libfprint-device-DEBUG: 05:03:23.287: Device reported open completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.287: Completing action FPI_DEVICE_ACTION_OPEN in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.287: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
192s (process:2568): libfprint-device-DEBUG: 05:03:23.287: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
192s (process:2568): libfprint-device-DEBUG: 05:03:23.287: Device reported finger status change: FP_FINGER_STATUS_NEEDED
192s (process:2568): libfprint-virtual_device_connection-DEBUG: 05:03:23.287: Got a new connection!
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.287: Got instructions of length 7
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.287: Received command UNPLUG 
192s (process:2568): libfprint-device-DEBUG: 05:03:23.387: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-device-DEBUG: 05:03:23.788: Device reported generic error (No commands arrived in time to run!) during action; action was: FPI_DEVICE_ACTION_VERIFY
192s (process:2568): libfprint-device-DEBUG: 05:03:23.788: Device reported verify completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.788: Device reported finger status change: FP_FINGER_STATUS_NONE
192s (process:2568): libfprint-device-DEBUG: 05:03:23.788: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.788: Updated temperature model after 0.40 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-device-DEBUG: 05:03:23.788: Device reported close completion
192s (process:2568): libfprint-device-DEBUG: 05:03:23.788: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
192s (process:2568): libfprint-device-DEBUG: 05:03:23.788: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.788: 70537560: ../libfprint/drivers/virtual-device.c:752
192s (process:2568): libfprint-virtual_device_storage-DEBUG: 05:03:23.788: 70537592: ../libfprint/drivers/virtual-device-storage.c:253
192s (process:2568): libfprint-virtual_device-DEBUG: 05:03:23.788: 70537612: ../libfprint/drivers/virtual-device.c:752
192s ok
192s 
192s ----------------------------------------------------------------------
192s Ran 86 tests in 17.467s
192s 
192s OK (skipped=1)
192s PASS: libfprint-2/virtual-device.test
192s Running test: libfprint-2/driver-focaltech_moc.test
192s ** (umockdev-run:2586): DEBUG: 05:03:23.830: umockdev.vala:127: Created udev test bed /tmp/umockdev.WK1712
192s ** (umockdev-run:2586): DEBUG: 05:03:23.830: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4
192s ** (umockdev-run:2586): DEBUG: 05:03:23.834: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1/3-1.4 (subsystem usb)
192s ** (umockdev-run:2586): DEBUG: 05:03:23.835: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WK1712/dev/bus/usb/003/006
192s ** (umockdev-run:2586): DEBUG: 05:03:23.836: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1
192s ** (umockdev-run:2586): DEBUG: 05:03:23.839: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3/3-1 (subsystem usb)
192s ** (umockdev-run:2586): DEBUG: 05:03:23.840: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WK1712/dev/bus/usb/003/002
192s ** (umockdev-run:2586): DEBUG: 05:03:23.840: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3
192s ** (umockdev-run:2586): DEBUG: 05:03:23.844: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0/usb3 (subsystem usb)
192s ** (umockdev-run:2586): DEBUG: 05:03:23.845: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.WK1712/dev/bus/usb/003/001
192s ** (umockdev-run:2586): DEBUG: 05:03:23.845: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0
192s ** (umockdev-run:2586): DEBUG: 05:03:23.847: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4/0000:0b:00.0 (subsystem pci)
192s ** (umockdev-run:2586): DEBUG: 05:03:23.848: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.4
192s ** (umockdev-run:2586): DEBUG: 05:03:23.849: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.4 (subsystem pci)
192s (process:2590): libfprint-context-DEBUG: 05:03:23.906: Initializing FpContext (libfprint version 1.94.9+tod1)
192s (process:2590): libfprint-tod-DEBUG: 05:03:23.906: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
192s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:23.907: 70656446: ../libfprint/drivers/focaltech_moc/focaltech_moc.c:1852
192s (process:2590): libfprint-context-DEBUG: 05:03:23.907: No driver found for USB device 05E3:0608
192s (process:2590): libfprint-context-DEBUG: 05:03:23.907: No driver found for USB device 1D6B:0002
192s (process:2590): libfprint-device-DEBUG: 05:03:23.908: Device reported probe completion
192s (process:2590): libfprint-device-DEBUG: 05:03:23.908: Completing action FPI_DEVICE_ACTION_PROBE in idle!
192s (process:2590): libfprint-device-DEBUG: 05:03:23.908: Not updating temperature model, device can run continuously!
192s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline?
192s libusb: warning [read_sysfs_attr] attribute bConfigurationValue doesn't end with newline?
192s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:23.908: class:dc, subclass:a0, protocol:b0
192s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:23.908: bytes size:0
192s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:23.908: kind:5, max packet size:64, poll interval:0, refresh:0, sync address:0, address:2, number:2, direction:G_USB_DEVICE_DIRECTION_HOST_TO_DEVICE
192s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:23.908: bytes size:0
192s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:23.908: kind:5, max packet size:64, poll interval:0, refresh:0, sync address:0, address:81, number:1, direction:G_USB_DEVICE_DIRECTION_DEVICE_TO_HOST
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.909: [focaltech_moc] DEV_INIT_STATES entering state 0
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.909: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.909: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
192s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:23.909: focaltechmoc enroll_times: 10
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.909: [focaltech_moc] DEV_INIT_STATES entering state 1
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.909: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.909: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.909: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.910: [focaltech_moc] DEV_INIT_STATES completed successfully
192s (process:2590): libfprint-device-DEBUG: 05:03:23.910: Device reported open completion
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.910: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
192s (process:2590): libfprint-device-DEBUG: 05:03:23.910: Completing action FPI_DEVICE_ACTION_OPEN in idle!
192s (process:2590): libfprint-device-DEBUG: 05:03:23.910: Not updating temperature model, device can run continuously!
192s (process:2590): libfprint-device-DEBUG: 05:03:23.910: Not updating temperature model, device can run continuously!
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.910: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 0
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.910: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.910: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.911: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 1
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.911: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.911: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.911: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.911: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 2
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.911: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.911: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.911: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.912: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 3
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.912: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.912: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.912: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
192s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:23.912: focaltechmoc user id: FP1-00000000-0-00000000-nobody
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.912: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.912: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.912: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.912: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.913: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.913: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.963: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.963: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.963: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.963: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
192s (process:2590): libfprint-SSM-DEBUG: 05:03:23.963: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.013: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.013: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.014: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.014: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.014: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.064: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.064: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.064: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.065: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.065: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.115: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.115: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.115: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.116: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.116: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.166: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.166: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.166: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.166: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.166: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.217: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.217: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.217: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.217: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.217: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.217: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.217: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-device-DEBUG: 05:03:24.218: Device reported enroll progress, reported 1 of 10 have been completed
193s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:24.218: focaltechmoc remain: 9
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.218: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.218: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.218: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.218: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.218: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.218: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s Executing: libfprint-2/driver-focaltech_moc.test
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.268: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.268: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.269: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.269: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.269: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.319: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.319: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.319: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.320: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.320: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.370: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.370: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.371: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.371: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.372: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.422: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.422: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.422: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.422: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.422: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.472: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.472: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.473: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.473: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.473: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.473: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.473: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-device-DEBUG: 05:03:24.473: Device reported enroll progress, reported 2 of 10 have been completed
193s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:24.474: focaltechmoc remain: 8
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.474: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.474: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.474: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.474: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.474: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.474: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.524: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.524: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.525: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.525: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.525: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.525: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.525: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-device-DEBUG: 05:03:24.525: Device reported enroll progress, reported 3 of 10 have been completed
193s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:24.525: focaltechmoc remain: 7
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.525: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.525: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.526: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.526: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.526: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.526: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.576: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.576: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.576: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.577: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.577: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.627: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.627: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.627: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.627: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.627: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.677: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.678: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.678: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.678: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.678: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.728: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.728: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.728: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.729: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.729: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.779: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.779: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.779: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.779: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.779: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.780: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.780: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-device-DEBUG: 05:03:24.780: Device reported enroll progress, reported 4 of 10 have been completed
193s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:24.780: focaltechmoc remain: 6
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.780: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.780: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.780: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.780: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.781: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.781: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.831: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.831: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.831: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.832: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.832: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.882: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.882: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.882: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.882: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.882: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.932: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.932: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.933: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.933: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.933: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.933: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.933: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-device-DEBUG: 05:03:24.934: Device reported enroll progress, reported 5 of 10 have been completed
193s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:24.934: focaltechmoc remain: 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.934: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.934: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.934: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.934: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.934: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
193s (process:2590): libfprint-SSM-DEBUG: 05:03:24.934: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:24.984: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:24.984: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:24.985: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:24.985: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
194s (process:2590): libfprint-SSM-DEBUG: 05:03:24.985: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.035: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.035: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.035: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.035: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.035: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.086: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.086: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.086: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.086: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.086: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.136: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.136: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.137: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.137: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.137: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.137: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.137: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-device-DEBUG: 05:03:25.137: Device reported enroll progress, reported 6 of 10 have been completed
194s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:25.137: focaltechmoc remain: 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.137: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.137: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.138: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.138: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.138: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.138: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.138: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.138: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-device-DEBUG: 05:03:25.138: Device reported enroll progress, reported 6 of 10 have been completed
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.138: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.138: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.139: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.139: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.139: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.139: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.189: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.189: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.189: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.190: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.190: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.240: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.240: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.240: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.240: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.240: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.290: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.290: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.291: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.291: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.291: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.341: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.341: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.342: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.342: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.342: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.342: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.342: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-device-DEBUG: 05:03:25.342: Device reported enroll progress, reported 7 of 10 have been completed
194s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:25.342: focaltechmoc remain: 3
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.342: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.342: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.343: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.343: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.343: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.343: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.393: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.393: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.393: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.394: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.394: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.444: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.444: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.444: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.444: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.444: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.444: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.445: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-device-DEBUG: 05:03:25.445: Device reported enroll progress, reported 8 of 10 have been completed
194s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:25.445: focaltechmoc remain: 2
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.445: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.445: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.445: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.445: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.446: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.446: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.496: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.496: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.496: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.496: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.496: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.496: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.496: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-device-DEBUG: 05:03:25.497: Device reported enroll progress, reported 9 of 10 have been completed
194s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:25.497: focaltechmoc remain: 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.497: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.497: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.497: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.497: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.497: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 5
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.497: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.547: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.548: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.548: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.548: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 6
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.548: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.548: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.548: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-device-DEBUG: 05:03:25.549: Device reported enroll progress, reported 10 of 10 have been completed
194s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:25.549: focaltechmoc remain: 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.549: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 7
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.549: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.549: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.549: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.549: [focaltech_moc] MOC_ENROLL_NUM_STATES entering state 8
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.549: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.549: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.549: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:25.550: focaltech_moc_commit_cb success
194s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:25.550: Enrollment was successful!
194s (process:2590): libfprint-device-DEBUG: 05:03:25.550: Device reported enroll completion
194s (process:2590): libfprint-device-DEBUG: 05:03:25.550: Print for finger FP_FINGER_UNKNOWN enrolled
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.550: [focaltech_moc] MOC_ENROLL_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.550: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-device-DEBUG: 05:03:25.550: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
194s (process:2590): libfprint-device-DEBUG: 05:03:25.550: Not updating temperature model, device can run continuously!
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.550: [focaltech_moc] MOC_LIST_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.550: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.550: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.551: [focaltech_moc] MOC_LIST_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.551: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.551: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.551: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:25.551: focaltechmoc add slot: 0
194s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:25.551: FP1-00000000-0-00000000-nobody
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.551: [focaltech_moc] MOC_LIST_NUM_STATES entering state 2
194s (process:2590): libfprint-device-DEBUG: 05:03:25.551: Device reported listing completion
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.551: [focaltech_moc] MOC_LIST_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.551: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-device-DEBUG: 05:03:25.551: Completing action FPI_DEVICE_ACTION_LIST in idle!
194s (process:2590): libfprint-device-DEBUG: 05:03:25.551: Not updating temperature model, device can run continuously!
194s (process:2590): libfprint-device-DEBUG: 05:03:25.551: Not updating temperature model, device can run continuously!
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.551: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.551: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.552: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.552: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.552: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.552: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.552: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.553: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.553: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.603: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.603: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.603: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.603: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.603: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.653: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.653: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.654: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.654: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.654: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.704: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.704: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.704: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.705: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.705: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.755: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.755: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.755: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.755: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.755: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.755: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.756: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.756: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.756: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.756: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.756: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-device-DEBUG: 05:03:25.756: Device reported verify result
194s (process:2590): libfprint-device-DEBUG: 05:03:25.756: Device reported verify completion
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.756: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.756: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-device-DEBUG: 05:03:25.756: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
194s (process:2590): libfprint-device-DEBUG: 05:03:25.756: Not updating temperature model, device can run continuously!
194s (process:2590): libfprint-device-DEBUG: 05:03:25.757: Not updating temperature model, device can run continuously!
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.757: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.757: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.758: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.758: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.758: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.758: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.758: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.759: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.759: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.809: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.809: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.809: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.809: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 2
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.809: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.859: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.859: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.860: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.860: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 3
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.860: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.860: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.860: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.861: [focaltech_moc] MOC_IDENTIFY_NUM_STATES entering state 4
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.861: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.861: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.861: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-device-DEBUG: 05:03:25.861: Device reported identify result
194s (process:2590): libfprint-device-DEBUG: 05:03:25.861: Device reported identify completion
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.861: [focaltech_moc] MOC_IDENTIFY_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.861: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-device-DEBUG: 05:03:25.861: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
194s (process:2590): libfprint-device-DEBUG: 05:03:25.861: Not updating temperature model, device can run continuously!
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.862: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.862: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.862: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.862: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.862: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.862: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.862: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:25.863: focaltechmoc add slot: 0
194s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:25.863: FP1-00000000-0-00000000-nobody
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.863: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 2
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.863: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.863: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.863: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.863: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.863: [focaltech_moc] FP_CMD_NUM_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.863: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.864: [focaltech_moc] FP_CMD_NUM_STATES entering state 1
194s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:25.864: delete slot 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.864: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 3
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.864: [focaltech_moc] MOC_DELETE_NUM_STATES entering state 4
194s (process:2590): libfprint-device-DEBUG: 05:03:25.864: Device reported deletion completion
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.864: [focaltech_moc] MOC_DELETE_NUM_STATES completed successfully
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.864: [focaltech_moc] FP_CMD_NUM_STATES completed successfully
194s (process:2590): libfprint-device-DEBUG: 05:03:25.864: Completing action FPI_DEVICE_ACTION_DELETE in idle!
194s (process:2590): libfprint-device-DEBUG: 05:03:25.864: Not updating temperature model, device can run continuously!
194s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:25.864: Focaltechmoc dev_exit
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.864: [focaltech_moc] DEV_EXIT_STATES entering state 0
194s (process:2590): libfprint-SSM-DEBUG: 05:03:25.864: [focaltech_moc] DEV_EXIT_STATES completed successfully
194s (process:2590): libfprint-focaltech_moc-DEBUG: 05:03:25.864: class:dc, subclass:a0, protocol:b0
194s (process:2590): libfprint-device-DEBUG: 05:03:25.864: Device reported close completion
194s (process:2590): libfprint-device-DEBUG: 05:03:25.864: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
194s (process:2590): libfprint-device-DEBUG: 05:03:25.864: Not updating temperature model, device can run continuously!
194s enrolling
194s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff812097c0 (FpiDeviceFocaltechMoc at 0x2f8dd30)>, 1, None, None, None)
194s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff812097c0 (FpiDeviceFocaltechMoc at 0x2f8dd30)>, 2, None, None, None)
194s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff812097c0 (FpiDeviceFocaltechMoc at 0x2f8dd30)>, 3, None, None, None)
194s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff812097c0 (FpiDeviceFocaltechMoc at 0x2f8dd30)>, 4, None, None, None)
194s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff812097c0 (FpiDeviceFocaltechMoc at 0x2f8dd30)>, 5, None, None, None)
194s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff812097c0 (FpiDeviceFocaltechMoc at 0x2f8dd30)>, 6, None, None, None)
194s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff812097c0 (FpiDeviceFocaltechMoc at 0x2f8dd30)>, 6, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
194s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff812097c0 (FpiDeviceFocaltechMoc at 0x2f8dd30)>, 7, None, None, None)
194s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff812097c0 (FpiDeviceFocaltechMoc at 0x2f8dd30)>, 8, None, None, None)
194s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff812097c0 (FpiDeviceFocaltechMoc at 0x2f8dd30)>, 9, None, None, None)
194s finger status:  <flags 0 of type FPrint.FingerStatusFlags>
194s enroll progress: (<__gi__.FpiDeviceFocaltechMoc object at 0x3ff812097c0 (FpiDeviceFocaltechMoc at 0x2f8dd30)>, 10, None, None, None)
194s enroll done
194s listing
194s listing done
194s verifying
194s verify done
194s async identifying
194s indentification_done:  <FPrint.Print object at 0x3ff81211280 (FpPrint at 0x2f8a750)> <FPrint.Print object at 0x3ff812112c0 (FpPrint at 0x2f94310)>
194s deleting
194s delete done
194s ** (umockdev-run:2586): DEBUG: 05:03:25.876: umockdev.vala:154: Removing test bed /tmp/umockdev.WK1712
194s (umockdev-run:2586): GLib-DEBUG: 05:03:25.880: unsetenv() is not thread-safe and should not be used after threads are created
194s PASS: libfprint-2/driver-focaltech_moc.test
194s Running test: libfprint-2/fp-context.test
194s TAP version 14
194s # random seed: R02S9ddb622de72f11ebfda8045dee3e710d
194s 1..9
194s # Start of context tests
194s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
194s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
194s ok 1 /context/new
194s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
194s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
194s ok 2 /context/no-devices
194s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
194s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
194s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
194s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-XAF612/virtual_image.socket
194s # libfprint-context-DEBUG: created
194s # libfprint-device-DEBUG: Device reported probe completion
194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
194s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
194s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
194s ok 3 /context/has-virtual-device
194s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
194s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
194s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
194s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-WMD612/virtual_image.socket
194s # libfprint-context-DEBUG: created
194s # libfprint-device-DEBUG: Device reported probe completion
194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
194s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
194s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
194s ok 4 /context/enumerates-new-devices
194s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
194s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
194s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
194s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-N1C612/virtual_image.socket
194s # libfprint-context-DEBUG: created
194s # libfprint-device-DEBUG: Device reported probe completion
194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
194s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
194s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
194s ok 5 /context/remove-device-closed
194s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
194s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
194s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
194s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-Z3C612/virtual_image.socket
194s # libfprint-context-DEBUG: created
194s # libfprint-device-DEBUG: Device reported probe completion
194s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
194s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
194s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2596): libfprint-virtual_image-DEBUG: 05:03:25.892: 72640793: ../libfprint/drivers/virtual-image.c:216
194s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2596): libfprint-virtual_device_connection-DEBUG: 05:03:25.892: 72640850: ../libfprint/drivers/virtual-device-listener.c:153
195s # libfprint-image_device-DEBUG: Image device open completed
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2596): libfprint-virtual_image-DEBUG: 05:03:25.992: 72741283: ../libfprint/drivers/virtual-image.c:244
195s # libfprint-image_device-DEBUG: Image device close completed
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
195s ok 6 /context/remove-device-closing
195s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
195s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
195s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
195s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-WZ7A22/virtual_image.socket
195s # libfprint-context-DEBUG: created
195s # libfprint-device-DEBUG: Device reported probe completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2596): libfprint-virtual_image-DEBUG: 05:03:26.093: 72842512: ../libfprint/drivers/virtual-image.c:216
195s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2596): libfprint-virtual_device_connection-DEBUG: 05:03:26.093: 72842540: ../libfprint/drivers/virtual-device-listener.c:153
195s # libfprint-image_device-DEBUG: Image device open completed
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2596): libfprint-virtual_image-DEBUG: 05:03:26.194: 72942997: ../libfprint/drivers/virtual-image.c:244
195s # libfprint-image_device-DEBUG: Image device close completed
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
195s ok 7 /context/remove-device-open
195s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
195s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
195s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
195s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-B44I22/virtual_image.socket
195s # libfprint-context-DEBUG: created
195s # libfprint-device-DEBUG: Device reported probe completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2596): libfprint-virtual_image-DEBUG: 05:03:26.295: 73044317: ../libfprint/drivers/virtual-image.c:216
195s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2596): libfprint-virtual_device_connection-DEBUG: 05:03:26.295: 73044341: ../libfprint/drivers/virtual-device-listener.c:153
195s # libfprint-image_device-DEBUG: Image device open completed
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2596): libfprint-virtual_image-DEBUG: 05:03:26.396: 73144676: ../libfprint/drivers/virtual-image.c:244
195s # libfprint-image_device-DEBUG: Image device close completed
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
195s ok 8 /context/remove-device-opening
195s # GLib-DEBUG: setenv()/putenv() are not thread-safe and should not be used after threads are created
195s # libfprint-context-DEBUG: Initializing FpContext (libfprint version 1.94.9+tod1)
195s # libfprint-tod-DEBUG: Impossible to load the shared drivers dir Error opening directory ?/usr/lib/s390x-linux-gnu/libfprint-2/tod-1?: No such file or directory
195s # libfprint-context-DEBUG: Found virtual environment device: FP_VIRTUAL_IMAGE, /tmp/libfprint-ZEHK22/virtual_image.socket
195s # libfprint-context-DEBUG: created
195s # libfprint-device-DEBUG: Device reported probe completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2596): libfprint-virtual_image-DEBUG: 05:03:26.497: 73245934: ../libfprint/drivers/virtual-image.c:216
195s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2596): libfprint-virtual_device_connection-DEBUG: 05:03:26.497: 73245960: ../libfprint/drivers/virtual-device-listener.c:153
195s # libfprint-image_device-DEBUG: Image device open completed
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-image_device-DEBUG: Activating image device
195s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
195s # libfprint-image_device-DEBUG: Image device activation completed
195s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
195s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
195s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED
195s # libfprint-image_device-DEBUG: Deactivating image device
195s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
195s # libfprint-image_device-DEBUG: Image device deactivation completed
195s # libfprint-image_device-DEBUG: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
195s # libfprint-device-DEBUG: Device reported generic error (The driver encountered a protocol error with the device.) during action; action was: FPI_DEVICE_ACTION_ENROLL
195s # libfprint-device-DEBUG: Device reported enroll completion
195s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s (/usr/libexec/installed-tests/libfprint-2/test-fp-context:2596): libfprint-virtual_image-DEBUG: 05:03:26.598: 73346672: ../libfprint/drivers/virtual-image.c:244
195s # libfprint-image_device-DEBUG: Image device close completed
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # GLib-DEBUG: unsetenv() is not thread-safe and should not be used after threads are created
195s ok 9 /context/remove-device-active
195s # End of context tests
195s PASS: libfprint-2/fp-context.test
195s Running test: libfprint-2/fpi-device.test
195s TAP version 14
195s # random seed: R02S27c8546ca6582cd90a8d0002ced1c626
195s 1..97
195s # Start of driver tests
195s ok 1 /driver/get_driver
195s ok 2 /driver/get_device_id
195s ok 3 /driver/get_name
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 4 /driver/is_open
195s ok 5 /driver/get_nr_enroll_stages
195s ok 6 /driver/set_nr_enroll_stages
195s ok 7 /driver/supports_identify
195s ok 8 /driver/supports_capture
195s ok 9 /driver/has_storage
195s ok 10 /driver/do_not_support_identify
195s ok 11 /driver/do_not_support_capture
195s ok 12 /driver/has_not_storage
195s ok 13 /driver/get_usb_device
195s ok 14 /driver/get_virtual_env
195s ok 15 /driver/get_driver_data
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
195s # 
195s # libfprint-device-DEBUG: Device reported probe completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 16 /driver/initial_features
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Probed device name in action FPI_DEVICE_ACTION_PROBE
195s # 
195s # libfprint-device-DEBUG: Device reported probe completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 17 /driver/probe
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 18 /driver/open
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 19 /driver/close
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
195s # 
195s # libfprint-device-DEBUG: Device reported enroll completion
195s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 20 /driver/enroll
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
195s # 
195s # libfprint-device-DEBUG: Device reported verify result
195s # libfprint-device-DEBUG: Device reported verify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 21 /driver/verify
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
195s # 
195s # libfprint-device-DEBUG: Device reported identify result
195s # libfprint-device-DEBUG: Device reported identify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 22 /driver/identify
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
195s # 
195s # libfprint-device-DEBUG: Device reported capture completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 23 /driver/capture
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
195s # 
195s # libfprint-device-DEBUG: Device reported listing completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 24 /driver/list
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
195s # 
195s # libfprint-device-DEBUG: Device reported deletion completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 25 /driver/delete
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
195s # 
195s # libfprint-device-DEBUG: Device reported deletion completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 26 /driver/clear_storage
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Idle cancelling on ongoing operation!
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
195s # 
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
195s # 
195s # libfprint-device-DEBUG: Device reported deletion completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 27 /driver/cancel
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Idle cancelling on ongoing operation!
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
195s # 
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
195s # 
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
195s # 
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
195s # 
195s # libfprint-device-DEBUG: Device reported verify result
195s # libfprint-device-DEBUG: Device reported verify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 28 /driver/critical
195s ok 29 /driver/get_current_action
195s ok 30 /driver/timeout
195s ok 31 /driver/error_types
195s ok 32 /driver/retry_error_types
195s # Start of get_scan_type tests
195s ok 33 /driver/get_scan_type/press
195s ok 34 /driver/get_scan_type/swipe
195s # End of get_scan_type tests
195s # Start of set_scan_type tests
195s ok 35 /driver/set_scan_type/press
195s ok 36 /driver/set_scan_type/swipe
195s # End of set_scan_type tests
195s # Start of finger_status tests
195s ok 37 /driver/finger_status/inactive
195s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED
195s ok 38 /driver/finger_status/waiting
195s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT
195s ok 39 /driver/finger_status/present
195s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED
195s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
195s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_PRESENT
195s # libfprint-device-DEBUG: Device reported finger status change: FP_FINGER_STATUS_NONE
195s ok 40 /driver/finger_status/changes
195s # End of finger_status tests
195s # Start of features tests
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_probe: Device Virtual device for debugging in action FPI_DEVICE_ACTION_PROBE
195s # 
195s # libfprint-device-DEBUG: Device reported probe completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 41 /driver/features/probe_updates
195s # End of features tests
195s # Start of initial_features tests
195s ok 42 /driver/initial_features/none
195s ok 43 /driver/initial_features/no_capture
195s ok 44 /driver/initial_features/no_verify
195s ok 45 /driver/initial_features/no_identify
195s ok 46 /driver/initial_features/no_storage
195s ok 47 /driver/initial_features/no_list
195s ok 48 /driver/initial_features/no_delete
195s ok 49 /driver/initial_features/no_clear
195s # End of initial_features tests
195s # Start of probe tests
195s # libfprint-device-DEBUG: Device reported probe completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 50 /driver/probe/error
195s # libfprint-device-DEBUG: Device reported generic error (The operation is not supported on this device!) during action; action was: FPI_DEVICE_ACTION_PROBE
195s # libfprint-device-DEBUG: Device reported probe completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_PROBE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 51 /driver/probe/action_error
195s # End of probe tests
195s # Start of open tests
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 52 /driver/open/error
195s # End of open tests
195s # Start of close tests
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 53 /driver/close/error
195s # End of close tests
195s # Start of enroll tests
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
195s # 
195s # libfprint-device-DEBUG: Device reported enroll completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 54 /driver/enroll/error
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Device reported enroll progress, reported 1797826663 of 610029345 have been completed
195s # libfprint-device-DEBUG: Device reported enroll progress, reported 1084628882 of 610029345 have been completed
195s # libfprint-device-DEBUG: Device reported enroll progress, reported 1587891230 of 610029345 have been completed
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
195s # 
195s # libfprint-device-DEBUG: Device reported enroll completion
195s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 55 /driver/enroll/progress
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
195s # 
195s # libfprint-device-DEBUG: Device reported enroll completion
195s # libfprint-device-DEBUG: Print for finger FP_FINGER_UNKNOWN enrolled
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 56 /driver/enroll/update_nbis
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 57 /driver/enroll/update_nbis_wrong_device
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 58 /driver/enroll/update_nbis_wrong_driver
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 59 /driver/enroll/update_nbis_missing_feature
195s # Start of error tests
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Device reported enroll completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s # libfprint-device-DEBUG: Device reported enroll completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s # libfprint-device-DEBUG: Device reported enroll completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 60 /driver/enroll/error/no_print
195s # End of error tests
195s # End of enroll tests
195s # Start of verify tests
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
195s # 
195s # libfprint-device-DEBUG: Device reported verify result
195s # libfprint-device-DEBUG: Device reported verify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 61 /driver/verify/fail
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
195s # 
195s # libfprint-device-DEBUG: Device reported verify result
195s # libfprint-device-DEBUG: Device reported verify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 62 /driver/verify/retry
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
195s # 
195s # libfprint-device-DEBUG: Device reported verify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 63 /driver/verify/error
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 64 /driver/verify/not_supported
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Device reported verify result
195s # libfprint-device-DEBUG: Device reported verify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 65 /driver/verify/report_no_cb
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Device reported verify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 66 /driver/verify/not_reported
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Device reported verify result
195s # libfprint-device-DEBUG: Device reported verify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s # libfprint-device-DEBUG: Device reported verify result
195s # libfprint-device-DEBUG: Device reported verify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s # libfprint-device-DEBUG: Device reported verify result
195s # libfprint-device-DEBUG: Device reported verify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s # libfprint-device-DEBUG: Device reported verify result
195s # libfprint-device-DEBUG: Device reported verify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s # libfprint-device-DEBUG: Device reported verify result
195s # libfprint-device-DEBUG: Device reported verify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 67 /driver/verify/complete_retry
195s # End of verify tests
195s # Start of identify tests
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
195s # 
195s # libfprint-device-DEBUG: Device reported identify result
195s # libfprint-device-DEBUG: Device reported identify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD
195s ok 68 /driver/identify/fail
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
195s # 
195s # libfprint-device-DEBUG: Device reported identify result
195s # libfprint-device-DEBUG: Device reported identify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 69 /driver/identify/retry
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
195s # 
195s # libfprint-device-DEBUG: Device reported identify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 70 /driver/identify/error
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Device reported identify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 71 /driver/identify/not_reported
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Device reported identify result
195s # libfprint-device-DEBUG: Device reported identify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Device reported identify result
195s # libfprint-device-DEBUG: Device reported identify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s # libfprint-device-DEBUG: Device reported identify result
195s # libfprint-device-DEBUG: Device reported identify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 72 /driver/identify/complete_retry
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Device reported identify result
195s # libfprint-device-DEBUG: Device reported identify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 73 /driver/identify/report_no_cb
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
195s # 
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_resume: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
195s # 
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
195s # 
195s # libfprint-device-DEBUG: Device reported identify result
195s # libfprint-device-DEBUG: Device reported identify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 74 /driver/identify/suspend_continues
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
195s # 
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
195s # 
195s # libfprint-device-DEBUG: Device reported identify result
195s # libfprint-device-DEBUG: Device reported identify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.01 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
195s ok 75 /driver/identify/suspend_succeeds
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_suspend: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
195s # 
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
195s # 
195s # libfprint-device-DEBUG: Device reported identify completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 76 /driver/identify/suspend_busy_error
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
195s # 
195s # libfprint-device-DEBUG: Device reported close completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s ok 77 /driver/identify/suspend_while_idle
195s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
195s # 
195s # libfprint-device-DEBUG: Device reported open completion
195s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
195s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
196s # libfprint-device-DEBUG: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.30, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
198s # libfprint-device-DEBUG: Updated temperature model after 2.00 seconds, ratio 0.30 -> 0.74, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_HOT
198s # libfprint-device-DEBUG: Idle cancelling on ongoing operation!
198s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_cancel: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
198s # 
198s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
198s # 
198s # libfprint-device-DEBUG: Device reported identify completion
198s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
198s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT
198s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 1 -> 1, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT
198s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.74 -> 0.74, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_HOT
198s Executing: libfprint-2/fpi-device.test
200s # libfprint-device-DEBUG: Updated temperature model after 2.09 seconds, ratio 0.74 -> 0.49, active 0 -> 0, FP_TEMPERATURE_HOT -> FP_TEMPERATURE_WARM
203s # libfprint-device-DEBUG: Updated temperature model after 3.10 seconds, ratio 0.49 -> 0.26, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.26 -> 0.26, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s ok 78 /driver/identify/warmup_cooldown
203s # slow test /driver/identify/warmup_cooldown executed in 7.29 secs
203s # End of identify tests
203s # Start of capture tests
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
203s # 
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s ok 79 /driver/capture/not_supported
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
203s # 
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
203s # 
203s # libfprint-device-DEBUG: Device reported capture completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s ok 80 /driver/capture/error
203s # End of capture tests
203s # Start of list tests
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
203s # 
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
203s # 
203s # libfprint-device-DEBUG: Device reported listing completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s ok 81 /driver/list/error
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
203s # 
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s ok 82 /driver/list/no_storage
203s # End of list tests
203s # Start of delete tests
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
203s # 
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
203s # 
203s # libfprint-device-DEBUG: Device reported deletion completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s ok 83 /driver/delete/error
203s # End of delete tests
203s # Start of clear_storage tests
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
203s # 
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
203s # 
203s # libfprint-device-DEBUG: Device reported deletion completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s ok 84 /driver/clear_storage/error
203s # End of clear_storage tests
203s # Start of cancel tests
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
203s # 
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
203s # 
203s # libfprint-device-DEBUG: Device reported deletion completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s ok 85 /driver/cancel/fail
203s # End of cancel tests
203s # Start of get_current_action tests
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s ok 86 /driver/get_current_action/open
203s # End of get_current_action tests
203s # Start of get_cancellable tests
203s ok 87 /driver/get_cancellable/error
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s ok 88 /driver/get_cancellable/open
203s # Start of open tests
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s ok 89 /driver/get_cancellable/open/internal
203s # End of open tests
203s # End of get_cancellable tests
203s # Start of action_is_cancelled tests
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s ok 90 /driver/action_is_cancelled/open
203s ok 91 /driver/action_is_cancelled/error
203s # Start of open tests
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s ok 92 /driver/action_is_cancelled/open/internal
203s # End of open tests
203s # End of action_is_cancelled tests
203s # Start of complete_action tests
203s # Start of all tests
203s ok 93 /driver/complete_action/all/error
203s # End of all tests
203s # End of complete_action tests
203s # Start of action_error tests
203s ok 94 /driver/action_error/error
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
203s # 
203s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_OPEN
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
203s # 
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
203s # 
203s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_ENROLL
203s # libfprint-device-DEBUG: Device reported enroll completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
203s # 
203s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_VERIFY
203s # libfprint-device-DEBUG: Device reported verify completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
203s # 
203s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_IDENTIFY
203s # libfprint-device-DEBUG: Device reported identify completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
203s # 
203s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CAPTURE
203s # libfprint-device-DEBUG: Device reported capture completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
203s # 
203s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_LIST
203s # libfprint-device-DEBUG: Device reported listing completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
203s # 
203s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_DELETE
203s # libfprint-device-DEBUG: Device reported deletion completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
203s # 
203s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLEAR_STORAGE
203s # libfprint-device-DEBUG: Device reported deletion completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported generic error (Passed (print) data is not valid.) during action; action was: FPI_DEVICE_ACTION_CLOSE
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s ok 95 /driver/action_error/all
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
203s # 
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_open: Device Virtual device for debugging in action FPI_DEVICE_ACTION_OPEN
203s # 
203s # libfprint-device-DEBUG: Device reported open completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_OPEN in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_enroll: Device Virtual device for debugging in action FPI_DEVICE_ACTION_ENROLL
203s # 
203s # libfprint-device-DEBUG: Device reported enroll completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_verify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_VERIFY
203s # 
203s # libfprint-device-DEBUG: Device reported verify completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_identify: Device Virtual device for debugging in action FPI_DEVICE_ACTION_IDENTIFY
203s # 
203s # libfprint-device-DEBUG: Device reported identify completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_capture: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CAPTURE
203s # 
203s # libfprint-device-DEBUG: Device reported capture completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_list: Device Virtual device for debugging in action FPI_DEVICE_ACTION_LIST
203s # 
203s # libfprint-device-DEBUG: Device reported listing completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_LIST in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_delete: Device Virtual device for debugging in action FPI_DEVICE_ACTION_DELETE
203s # 
203s # libfprint-device-DEBUG: Device reported deletion completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_DELETE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_clear_storage: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLEAR_STORAGE
203s # 
203s # libfprint-device-DEBUG: Device reported deletion completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s # libfprint-fake_test_dev-DEBUG: fpi_device_fake_close: Device Virtual device for debugging in action FPI_DEVICE_ACTION_CLOSE
203s # 
203s # libfprint-device-DEBUG: Device reported close completion
203s # libfprint-device-DEBUG: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
203s # libfprint-device-DEBUG: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
203s ok 96 /driver/action_error/fail
203s # End of action_error tests
203s # Start of timeout tests
203s ok 97 /driver/timeout/cancelled
203s # End of timeout tests
203s # End of driver tests
203s PASS: libfprint-2/fpi-device.test
203s Running test: libfprint-2/fpi-assembling.test
203s TAP version 14
203s # random seed: R02S40f08490ad67971b51163b565937fc8b
203s 1..1
203s # Start of assembling tests
203s not ok /assembling/frames - libfprint:ERROR:../tests/test-fpi-assembling.c:76:test_frame_assembling: assertion failed (cairo_image_surface_get_format (img) == CAIRO_FORMAT_RGB24): (0 == 1)
203s Bail out!
203s **
203s libfprint:ERROR:../tests/test-fpi-assembling.c:76:test_frame_assembling: assertion failed (cairo_image_surface_get_format (img) == CAIRO_FORMAT_RGB24): (0 == 1)
203s Executing: libfprint-2/fpi-assembling.test
204s FAIL: libfprint-2/fpi-assembling.test (Child process killed by signal 6)
204s Running test: libfprint-2/fpi-ssm.test
204s TAP version 14
204s # random seed: R02S241b684d1d2c47acedb7261a74ad942a
204s 1..42
204s # Start of ssm tests
204s ok 1 /ssm/new
204s ok 2 /ssm/set_data
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s ok 3 /ssm/start
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
204s ok 4 /ssm/next
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
204s ok 5 /ssm/jump_to_state
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
204s ok 6 /ssm/mark_completed
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # 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.
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
204s ok 7 /ssm/mark_failed
204s # Start of new tests
204s ok 8 /ssm/new/full
204s ok 9 /ssm/new/no_handler
204s ok 10 /ssm/new/wrong_states
204s # End of new tests
204s # Start of set_data tests
204s ok 11 /ssm/set_data/cleanup
204s # End of set_data tests
204s # Start of start tests
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM_SINGLE_STATE completed successfully
204s ok 12 /ssm/start/single
204s # End of start tests
204s # Start of next tests
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
204s ok 13 /ssm/next/complete
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
204s ok 14 /ssm/next/not_started
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
204s ok 15 /ssm/next/with_delayed
204s # End of next tests
204s # Start of jump_to_state tests
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
204s ok 16 /ssm/jump_to_state/not_started
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
204s ok 17 /ssm/jump_to_state/with_delayed
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
204s ok 18 /ssm/jump_to_state/last
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10
204s ok 19 /ssm/jump_to_state/wrong
204s # End of jump_to_state tests
204s # Start of mark_completed tests
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
204s ok 20 /ssm/mark_completed/not_started
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
204s ok 21 /ssm/mark_completed/with_delayed
204s # End of mark_completed tests
204s # Start of mark_failed tests
204s # 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.
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
204s ok 22 /ssm/mark_failed/not_started
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # 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.
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The driver encountered a protocol error with the device.
204s ok 23 /ssm/mark_failed/with_delayed
204s # End of mark_failed tests
204s # Start of delayed tests
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
204s ok 24 /ssm/delayed/next
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
204s ok 25 /ssm/delayed/jump_to_state
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
204s ok 26 /ssm/delayed/mark_completed
204s # Start of next tests
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
204s ok 27 /ssm/delayed/next/cancel
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
204s ok 28 /ssm/delayed/next/not_started
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
204s ok 29 /ssm/delayed/next/complete
204s # End of next tests
204s # Start of jump_to_state tests
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
204s ok 30 /ssm/delayed/jump_to_state/cancel
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
204s ok 31 /ssm/delayed/jump_to_state/not_started
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
204s ok 32 /ssm/delayed/jump_to_state/last
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 14
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state -10
204s ok 33 /ssm/delayed/jump_to_state/wrong
204s # End of jump_to_state tests
204s # Start of mark_completed tests
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
204s ok 34 /ssm/delayed/mark_completed/cancel
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
204s ok 35 /ssm/delayed/mark_completed/not_started
204s # End of mark_completed tests
204s # Start of cancel tests
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM cancelled delayed state change
204s ok 36 /ssm/delayed/cancel/error
204s # End of cancel tests
204s # End of delayed tests
204s # Start of subssm tests
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 1
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
204s ok 37 /ssm/subssm/start
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
204s # 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.
204s # 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.
204s # 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.
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: The device is still busy with another operation, please try again later.
204s ok 38 /ssm/subssm/mark_failed
204s # Start of start tests
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
204s ok 39 /ssm/subssm/start/with_started
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
204s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM entering state 0
205s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SUB_SSM completed successfully
205s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 1
205s ok 40 /ssm/subssm/start/with_delayed
205s # End of start tests
205s # End of subssm tests
205s # Start of cleanup tests
205s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
205s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
205s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
205s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed successfully
205s ok 41 /ssm/cleanup/complete
205s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 0
205s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 0 with error: non-cleanup
205s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 2
205s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 2 (cleanup) with error: cleanup 1
205s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM entering state 3
205s # libfprint-SSM-DEBUG: [fake_test_dev] SSM FPI_TEST_SSM failed in state 3 (cleanup) with error: cleanup 2
205s # libfprint-SSM-DEBUG: [fake_test_dev] FPI_TEST_SSM completed with error: non-cleanup
205s ok 42 /ssm/cleanup/fail
205s # End of cleanup tests
205s # End of ssm tests
205s PASS: libfprint-2/fpi-ssm.test
205s Running test: libfprint-2/driver-realtek-5816.test
205s ** (umockdev-run:2634): DEBUG: 05:03:36.077: umockdev.vala:127: Created udev test bed /tmp/umockdev.IBKB22
205s ** (umockdev-run:2634): DEBUG: 05:03:36.078: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-6
205s ** (umockdev-run:2634): DEBUG: 05:03:36.079: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-6 (subsystem usb)
205s ** (umockdev-run:2634): DEBUG: 05:03:36.081: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IBKB22/dev/bus/usb/001/006
205s ** (umockdev-run:2634): DEBUG: 05:03:36.081: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
205s ** (umockdev-run:2634): DEBUG: 05:03:36.082: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
205s ** (umockdev-run:2634): DEBUG: 05:03:36.083: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IBKB22/dev/bus/usb/001/001
205s ** (umockdev-run:2634): DEBUG: 05:03:36.083: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0
205s ** (umockdev-run:2634): DEBUG: 05:03:36.083: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
205s (process:2638): libfprint-context-DEBUG: 05:03:36.144: Initializing FpContext (libfprint version 1.94.9+tod1)
205s (process:2638): libfprint-tod-DEBUG: 05:03:36.144: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
205s (process:2638): libfprint-context-DEBUG: 05:03:36.145: No driver found for USB device 1D6B:0002
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.145: 82894405: ../libfprint/drivers/realtek/realtek.c:1224
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.147: Device name: Realtek USB2.0 Finger Print Bridge
205s (process:2638): libfprint-device-DEBUG: 05:03:36.147: Device reported probe completion
205s (process:2638): libfprint-device-DEBUG: 05:03:36.147: Completing action FPI_DEVICE_ACTION_PROBE in idle!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.147: Not updating temperature model, device can run continuously!
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.148: 82896768: ../libfprint/drivers/realtek/realtek.c:1269
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.148: [realtek] Init entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.148: [realtek] Init entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.148: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.148: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.148: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.149: [realtek] Init entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.149: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.149: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.149: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.149: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.149: [realtek] Init completed successfully
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.149: Init complete!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.149: Device reported open completion
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.149: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-device-DEBUG: 05:03:36.149: Completing action FPI_DEVICE_ACTION_OPEN in idle!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.149: Not updating temperature model, device can run continuously!
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.149: 82898619: ../libfprint/drivers/realtek/realtek.c:1332
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.149: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.150: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.150: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.150: Successfully cleared storage
205s (process:2638): libfprint-device-DEBUG: 05:03:36.150: Device reported deletion completion
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.150: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-device-DEBUG: 05:03:36.150: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.150: Not updating temperature model, device can run continuously!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.150: Not updating temperature model, device can run continuously!
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.150: 82899483: ../libfprint/drivers/realtek/realtek.c:1201
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.150: [realtek] Enroll entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.150: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.151: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.151: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.151: [realtek] Enroll entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.151: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.151: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.151: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.151: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.152: [realtek] Enroll entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.152: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.152: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.152: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.152: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.152: [realtek] Enroll entering state 3
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.152: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.152: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.152: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.153: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.153: Device reported finger status change: FP_FINGER_STATUS_PRESENT
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.153: [realtek] Enroll entering state 4
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.153: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.153: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.153: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.153: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.154: Device reported finger status change: FP_FINGER_STATUS_NONE
205s (process:2638): libfprint-device-DEBUG: 05:03:36.154: Device reported enroll progress, reported 1 of 8 have been completed
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.154: [realtek] Enroll entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.154: Device reported finger status change: FP_FINGER_STATUS_NEEDED
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.154: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.154: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.154: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.154: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.154: [realtek] Enroll entering state 3
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.154: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.154: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.154: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.155: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.155: Device reported finger status change: FP_FINGER_STATUS_PRESENT
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.155: [realtek] Enroll entering state 4
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.155: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.155: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.155: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.155: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.156: Device reported finger status change: FP_FINGER_STATUS_NONE
205s (process:2638): libfprint-device-DEBUG: 05:03:36.156: Device reported enroll progress, reported 2 of 8 have been completed
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.156: [realtek] Enroll entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.156: Device reported finger status change: FP_FINGER_STATUS_NEEDED
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.156: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.156: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.156: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.156: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.156: [realtek] Enroll entering state 3
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.156: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.156: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.156: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.156: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.157: Device reported finger status change: FP_FINGER_STATUS_PRESENT
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.157: [realtek] Enroll entering state 4
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.157: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.157: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.157: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.157: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.157: Device reported finger status change: FP_FINGER_STATUS_NONE
205s (process:2638): libfprint-device-DEBUG: 05:03:36.157: Device reported enroll progress, reported 3 of 8 have been completed
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.157: [realtek] Enroll entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.157: Device reported finger status change: FP_FINGER_STATUS_NEEDED
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.157: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.158: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.158: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.158: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.158: [realtek] Enroll entering state 3
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.158: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.158: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.158: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.158: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.159: Device reported finger status change: FP_FINGER_STATUS_PRESENT
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.159: [realtek] Enroll entering state 4
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.159: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.159: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.159: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.159: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.159: Device reported finger status change: FP_FINGER_STATUS_NONE
205s (process:2638): libfprint-device-DEBUG: 05:03:36.159: Device reported enroll progress, reported 4 of 8 have been completed
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.159: [realtek] Enroll entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.159: Device reported finger status change: FP_FINGER_STATUS_NEEDED
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.159: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.159: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.160: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.160: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.160: [realtek] Enroll entering state 3
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.160: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.160: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.160: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.160: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.160: Device reported finger status change: FP_FINGER_STATUS_PRESENT
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.160: [realtek] Enroll entering state 4
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.160: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.161: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.161: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.161: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.161: Device reported finger status change: FP_FINGER_STATUS_NONE
205s (process:2638): libfprint-device-DEBUG: 05:03:36.161: Device reported enroll progress, reported 5 of 8 have been completed
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.161: [realtek] Enroll entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.161: Device reported finger status change: FP_FINGER_STATUS_NEEDED
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.161: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.161: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.162: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.162: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.162: [realtek] Enroll entering state 3
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.162: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.162: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.162: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.162: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.163: Device reported finger status change: FP_FINGER_STATUS_PRESENT
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.163: [realtek] Enroll entering state 4
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.163: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.163: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.163: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.163: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.163: Device reported finger status change: FP_FINGER_STATUS_NONE
205s (process:2638): libfprint-device-DEBUG: 05:03:36.163: Device reported enroll progress, reported 6 of 8 have been completed
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.163: [realtek] Enroll entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.163: Device reported finger status change: FP_FINGER_STATUS_NEEDED
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.163: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.163: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.163: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.164: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.164: [realtek] Enroll entering state 3
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.164: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.164: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.164: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.164: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.164: Device reported finger status change: FP_FINGER_STATUS_PRESENT
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.164: [realtek] Enroll entering state 4
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.164: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.165: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.165: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.165: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.165: Device reported finger status change: FP_FINGER_STATUS_NONE
205s (process:2638): libfprint-device-DEBUG: 05:03:36.165: Device reported enroll progress, reported 7 of 8 have been completed
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.165: [realtek] Enroll entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.165: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.165: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.165: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.165: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.166: [realtek] Enroll entering state 3
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.166: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.166: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.166: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.166: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.166: Device reported finger status change: FP_FINGER_STATUS_PRESENT
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.166: [realtek] Enroll entering state 4
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.166: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.167: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.167: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.167: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.167: Device reported finger status change: FP_FINGER_STATUS_NONE
205s (process:2638): libfprint-device-DEBUG: 05:03:36.167: Device reported enroll progress, reported 8 of 8 have been completed
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.167: [realtek] Enroll entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.167: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.167: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.167: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.167: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.168: [realtek] Enroll entering state 3
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.168: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.168: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.168: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.168: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.168: Device reported finger status change: FP_FINGER_STATUS_PRESENT
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.168: [realtek] Enroll entering state 4
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.168: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.169: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.169: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.169: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.169: Device reported finger status change: FP_FINGER_STATUS_NONE
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.169: [realtek] Enroll entering state 5
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.169: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.169: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.169: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.170: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.170: [realtek] Enroll entering state 6
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.170: user_id: FP1-00000000-0-00000000-nobody, finger: 0xff
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.170: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.170: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.170: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.170: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.171: [realtek] Enroll completed successfully
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.171: Enrollment complete!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.171: Device reported enroll completion
205s (process:2638): libfprint-device-DEBUG: 05:03:36.171: Print for finger FP_FINGER_UNKNOWN enrolled
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.171: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-device-DEBUG: 05:03:36.171: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.171: Not updating temperature model, device can run continuously!
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.171: 82919884: ../libfprint/drivers/realtek/realtek.c:1344
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.171: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.171: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.171: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.172: Query templates complete!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.172: Device reported listing completion
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.172: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-device-DEBUG: 05:03:36.172: Completing action FPI_DEVICE_ACTION_LIST in idle!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.172: Not updating temperature model, device can run continuously!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.172: Not updating temperature model, device can run continuously!
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.172: 82920809: ../libfprint/drivers/realtek/realtek.c:1177
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.172: [realtek] Verify & Identify entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.172: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.172: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.172: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.172: [realtek] Verify & Identify entering state 1
205s (process:2638): libfprint-device-DEBUG: 05:03:36.172: Device reported finger status change: FP_FINGER_STATUS_NEEDED
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.172: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.173: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.173: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.173: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.173: [realtek] Verify & Identify entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.173: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.173: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.173: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.173: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.174: Device reported finger status change: FP_FINGER_STATUS_PRESENT
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.174: [realtek] Verify & Identify entering state 3
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.174: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.174: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.174: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.174: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.174: Device reported finger status change: FP_FINGER_STATUS_NONE
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.174: [realtek] Verify & Identify entering state 4
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.174: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.175: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.175: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.175: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.175: Device reported verify result
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.175: [realtek] Verify & Identify entering state 5
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.175: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.175: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.175: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.175: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.176: [realtek] Verify & Identify completed successfully
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.176: Verify complete!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.176: Device reported verify completion
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.176: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-device-DEBUG: 05:03:36.176: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.176: Not updating temperature model, device can run continuously!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.176: Not updating temperature model, device can run continuously!
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.176: 82925105: ../libfprint/drivers/realtek/realtek.c:1177
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.176: [realtek] Verify & Identify entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.176: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.176: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.176: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.177: [realtek] Verify & Identify entering state 1
205s (process:2638): libfprint-device-DEBUG: 05:03:36.177: Device reported finger status change: FP_FINGER_STATUS_NEEDED
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.177: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.177: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.177: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.177: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.177: [realtek] Verify & Identify entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.177: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.177: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.177: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.178: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.178: Device reported finger status change: FP_FINGER_STATUS_PRESENT
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.178: [realtek] Verify & Identify entering state 3
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.178: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.178: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.178: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.178: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.179: Device reported finger status change: FP_FINGER_STATUS_NONE
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.179: [realtek] Verify & Identify entering state 4
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.179: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.179: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.179: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.179: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-device-DEBUG: 05:03:36.179: Device reported identify result
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.179: [realtek] Verify & Identify completed successfully
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.179: Verify complete!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.179: Device reported identify completion
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.179: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-device-DEBUG: 05:03:36.179: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.179: Not updating temperature model, device can run continuously!
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.180: 82928796: ../libfprint/drivers/realtek/realtek.c:1313
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.180: [realtek] Delete print entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.180: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.180: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.180: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.180: [realtek] Delete print entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.180: [realtek] FP_RTK_CMD_NUM_STATES entering state 0
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.181: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.181: [realtek] FP_RTK_CMD_NUM_STATES entering state 1
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.181: [realtek] FP_RTK_CMD_NUM_STATES entering state 2
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.181: [realtek] Delete print completed successfully
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.181: Delete print complete!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.181: Device reported deletion completion
205s (process:2638): libfprint-SSM-DEBUG: 05:03:36.181: [realtek] FP_RTK_CMD_NUM_STATES completed successfully
205s (process:2638): libfprint-device-DEBUG: 05:03:36.181: Completing action FPI_DEVICE_ACTION_DELETE in idle!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.181: Not updating temperature model, device can run continuously!
205s (process:2638): libfprint-realtek-DEBUG: 05:03:36.181: 82930169: ../libfprint/drivers/realtek/realtek.c:1301
205s (process:2638): libfprint-device-DEBUG: 05:03:36.181: Device reported close completion
205s (process:2638): libfprint-device-DEBUG: 05:03:36.181: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
205s (process:2638): libfprint-device-DEBUG: 05:03:36.181: Not updating temperature model, device can run continuously!
205s enrolling
205s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb900a340 (FpiDeviceRealtek at 0x1e7f6f0)>, 1, None, None, None)
205s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb900a340 (FpiDeviceRealtek at 0x1e7f6f0)>, 2, None, None, None)
205s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb900a340 (FpiDeviceRealtek at 0x1e7f6f0)>, 3, None, None, None)
205s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb900a340 (FpiDeviceRealtek at 0x1e7f6f0)>, 4, None, None, None)
205s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb900a340 (FpiDeviceRealtek at 0x1e7f6f0)>, 5, None, None, None)
205s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb900a340 (FpiDeviceRealtek at 0x1e7f6f0)>, 6, None, None, None)
205s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb900a340 (FpiDeviceRealtek at 0x1e7f6f0)>, 7, None, None, None)
205s enroll progress: (<__gi__.FpiDeviceRealtek object at 0x3ffb900a340 (FpiDeviceRealtek at 0x1e7f6f0)>, 8, None, None, None)
205s enroll done
205s listing
205s listing done
205s verifying
205s verify done
205s async identifying
205s indentification_done:  <FPrint.Print object at 0x3ffb9011b40 (FpPrint at 0x1e7c750)> <FPrint.Print object at 0x3ffb9011b80 (FpPrint at 0x1e84e20)>
205s deleting
205s delete done
205s ** (umockdev-run:2634): DEBUG: 05:03:36.191: umockdev.vala:154: Removing test bed /tmp/umockdev.IBKB22
205s (umockdev-run:2634): GLib-DEBUG: 05:03:36.193: unsetenv() is not thread-safe and should not be used after threads are created
205s PASS: libfprint-2/driver-realtek-5816.test
205s Running test: libfprint-2/driver-egis0570.test
205s ** (umockdev-run:2646): DEBUG: 05:03:36.222: umockdev.vala:127: Created udev test bed /tmp/umockdev.IN2D22
205s ** (umockdev-run:2646): DEBUG: 05:03:36.222: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1/1-9
205s ** (umockdev-run:2646): DEBUG: 05:03:36.223: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1/1-9 (subsystem usb)
205s ** (umockdev-run:2646): DEBUG: 05:03:36.225: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IN2D22/dev/bus/usb/001/005
205s ** (umockdev-run:2646): DEBUG: 05:03:36.225: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb1
205s ** (umockdev-run:2646): DEBUG: 05:03:36.225: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb1 (subsystem usb)
205s ** (umockdev-run:2646): DEBUG: 05:03:36.227: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.IN2D22/dev/bus/usb/001/001
205s ** (umockdev-run:2646): DEBUG: 05:03:36.227: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0
205s ** (umockdev-run:2646): DEBUG: 05:03:36.227: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
205s (process:2650): libfprint-context-DEBUG: 05:03:36.285: Initializing FpContext (libfprint version 1.94.9+tod1)
205s (process:2650): libfprint-tod-DEBUG: 05:03:36.285: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
205s (process:2650): libfprint-context-DEBUG: 05:03:36.286: No driver found for USB device 1D6B:0002
205s (process:2650): libfprint-device-DEBUG: 05:03:36.286: Device reported probe completion
205s (process:2650): libfprint-device-DEBUG: 05:03:36.286: Completing action FPI_DEVICE_ACTION_PROBE in idle!
205s (process:2650): libfprint-device-DEBUG: 05:03:36.286: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.287: Image device open completed
205s (process:2650): libfprint-device-DEBUG: 05:03:36.287: Device reported open completion
205s (process:2650): libfprint-device-DEBUG: 05:03:36.287: Completing action FPI_DEVICE_ACTION_OPEN in idle!
205s (process:2650): libfprint-device-DEBUG: 05:03:36.287: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
205s (process:2650): libfprint-device-DEBUG: 05:03:36.287: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.287: Activating image device
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.287: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.287: [egis0570] SM_STATES_NUM entering state 0
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.287: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.287: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.287: Image device activation completed
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.287: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.287: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
205s (process:2650): libfprint-device-DEBUG: 05:03:36.287: Device reported finger status change: FP_FINGER_STATUS_NEEDED
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.287: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.288: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.288: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.288: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.288: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.289: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.289: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.289: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.290: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.290: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.290: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.290: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.291: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.291: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.291: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.292: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.292: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.292: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.292: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.293: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.293: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.293: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.294: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.294: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.294: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.295: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.295: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.295: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.295: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.296: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.296: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.296: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.297: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.297: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.297: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.298: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.298: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.298: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.299: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.299: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.299: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.299: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.300: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.300: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.300: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.300: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.301: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.301: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.301: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.301: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.301: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.301: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.302: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.302: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.302: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.303: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.303: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.303: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.303: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.303: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.303: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.303: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.303: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.303: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.303: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.303: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.303: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.304: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.304: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.304: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.304: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.305: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.305: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.306: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.306: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.306: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.306: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.306: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.306: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.306: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.306: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.306: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.306: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.306: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.306: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.306: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.307: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.307: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.308: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.308: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.308: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.308: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.309: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.309: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.309: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.309: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.309: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.309: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.309: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.309: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.309: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.309: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.309: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.310: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.310: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.310: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.311: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.311: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.311: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.311: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.311: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.311: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.311: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.311: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.311: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.311: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.311: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.311: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.311: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.312: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.312: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.312: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.313: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.313: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.314: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.314: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.314: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.314: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.314: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.314: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.314: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.314: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.314: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.314: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.314: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.315: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.315: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.315: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.315: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.316: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.316: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.316: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.316: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.317: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.317: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.317: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.317: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.317: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.317: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.317: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.317: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.317: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.317: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.317: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.318: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.318: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.318: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.318: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.319: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.319: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.319: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.319: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.319: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.319: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.319: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.319: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.319: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.319: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.319: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.319: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.320: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.320: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.320: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.320: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.321: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.321: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.321: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.321: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.321: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.321: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.321: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.321: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.321: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.321: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.321: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.321: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.321: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.322: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.322: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.322: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.323: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.323: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.323: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.323: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.323: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.323: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.324: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.324: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.324: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.324: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.324: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.324: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.324: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.324: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.324: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.324: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.324: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.325: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.325: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.325: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.325: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.326: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.326: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.326: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.326: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.326: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.326: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.326: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.326: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.326: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.326: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.326: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.327: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.327: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.327: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.327: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.328: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.328: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.328: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.328: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.328: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.328: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.328: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.328: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.328: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.328: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.328: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.328: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.328: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.329: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.329: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.329: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.330: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.330: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.330: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.330: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.330: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.330: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.330: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.330: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.330: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.330: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.330: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.330: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.330: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.331: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.331: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.331: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.332: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.332: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.332: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.332: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.332: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.332: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.332: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.332: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.332: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.332: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.332: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.332: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.332: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.333: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.333: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.333: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.333: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.334: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.334: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.334: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.334: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.335: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.335: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.335: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.335: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.335: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.335: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.335: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.335: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.335: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.335: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.335: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.336: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.336: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.336: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.336: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.337: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.337: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.337: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.337: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.337: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.337: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.337: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.337: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.337: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.337: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.337: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.337: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.337: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.338: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.338: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.338: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.339: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.339: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.339: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.339: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.339: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.339: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.339: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.339: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.339: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.339: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.339: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.339: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.339: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.340: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.340: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.340: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.341: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.341: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.341: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.341: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.341: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.341: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.341: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.341: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.341: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.341: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.341: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.341: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.341: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.342: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.342: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.342: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.342: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.343: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.343: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.343: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.343: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.344: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.344: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.344: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.344: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.344: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.344: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.344: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.344: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.344: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.344: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.344: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.344: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.345: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.345: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.345: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.346: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.346: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.346: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.346: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.346: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.346: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.346: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.346: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.346: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.346: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.346: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.346: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.346: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.347: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.347: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.347: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.347: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.348: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.348: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.348: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.348: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.348: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.348: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.348: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.348: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.348: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.348: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.348: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.348: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.348: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.349: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.349: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.350: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.350: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.350: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.350: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.350: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.350: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.350: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.350: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.350: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.350: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.350: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.350: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.350: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.351: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.351: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.351: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.351: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.352: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.352: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.352: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.352: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.353: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.353: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.353: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.353: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.353: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.353: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.353: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.353: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.353: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.353: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.353: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.353: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.354: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.354: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.354: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.355: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.355: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.355: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.355: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.355: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.355: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.355: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.355: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.355: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.355: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.355: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.355: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.355: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.356: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.356: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.356: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.356: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.357: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.357: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.357: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.357: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.357: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.357: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.357: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.357: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.357: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.357: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.357: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.357: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.357: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.358: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.358: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.358: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.358: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.359: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.359: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.359: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.359: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.359: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.359: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.359: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.359: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.359: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.359: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.359: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.359: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.359: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.360: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.360: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.360: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.361: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.361: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.361: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.361: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.361: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.361: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.361: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.361: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.361: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.361: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.361: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.361: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.362: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.362: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.362: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.362: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.363: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.363: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.363: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.363: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.364: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.364: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.364: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.364: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.364: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.364: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.364: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.364: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.364: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.364: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.364: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.365: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.365: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.365: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.365: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.366: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.366: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.366: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.366: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.366: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.366: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.366: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.366: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.366: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.366: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.366: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.366: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.366: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.367: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.367: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.367: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.368: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.368: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.368: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.368: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.368: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.368: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.368: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.368: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.368: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.368: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.368: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.368: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.368: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.369: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.369: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.369: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.369: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.370: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.370: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.370: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.370: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.370: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.370: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.370: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.370: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.370: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.370: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.370: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.370: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.370: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.371: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.371: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.371: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.371: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.372: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.372: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.372: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.372: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.372: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.372: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.372: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.372: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.372: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.372: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.372: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.372: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.373: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.373: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.373: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.373: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.374: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.374: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.374: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.374: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.375: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.375: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.375: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.375: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.375: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.375: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.375: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.375: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.375: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.375: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.375: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.375: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.376: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.376: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.376: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.377: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.377: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.377: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.377: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.377: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.377: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.377: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.377: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.377: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.377: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.377: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.377: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.377: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.378: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.378: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.378: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.378: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.379: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.379: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.379: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.379: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.379: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.379: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.379: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.379: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.379: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.379: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.379: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.379: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.380: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.380: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.380: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.380: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.381: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.381: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.381: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.381: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.381: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.381: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.381: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.381: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.381: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.381: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.381: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.381: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.381: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.382: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.382: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.382: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.383: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.383: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.383: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.383: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.383: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.383: Finger status (picture number, mean) : 1 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.384: Finger status (picture number, mean) : 2 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.384: Finger status (picture number, mean) : 3 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.384: Finger status (picture number, mean) : 4 , 0
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.384: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.384: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.384: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.384: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.384: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.384: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.384: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.385: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.385: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.385: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.385: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.385: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.386: Finger status (picture number, mean) : 0 , 0
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.386: Finger status (picture number, mean) : 1 , 1
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.386: Finger status (picture number, mean) : 2 , 2
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.386: Finger status (picture number, mean) : 3 , 3
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.386: Finger status (picture number, mean) : 4 , 6
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.386: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.386: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.386: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.386: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.386: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.386: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.386: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.387: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-device-DEBUG: 05:03:36.387: Updated temperature model after 0.10 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.387: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.387: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.388: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.388: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.388: Finger status (picture number, mean) : 0 , 11
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.388: Finger status (picture number, mean) : 1 , 16
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.388: Finger status (picture number, mean) : 2 , 23
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.388: Finger status (picture number, mean) : 3 , 28
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.388: Finger status (picture number, mean) : 4 , 32
205s (process:2650): libfprint-device-DEBUG: 05:03:36.388: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.388: Image device reported finger status: on
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.388: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
205s (process:2650): libfprint-device-DEBUG: 05:03:36.388: Device reported finger status change: FP_FINGER_STATUS_NEEDED
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.388: Image device reported finger status: off
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.388: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.388: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.388: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.388: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.388: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.389: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.389: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.389: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.389: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.390: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.390: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.390: Finger status (picture number, mean) : 0 , 38
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.390: Finger status (picture number, mean) : 1 , 43
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.390: Finger status (picture number, mean) : 2 , 48
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.390: Finger status (picture number, mean) : 3 , 54
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.390: Finger status (picture number, mean) : 4 , 58
205s (process:2650): libfprint-device-DEBUG: 05:03:36.390: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.390: Image device reported finger status: on
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.390: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.390: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.390: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.390: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.391: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.391: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.391: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.392: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.392: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.392: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.392: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.392: Finger status (picture number, mean) : 0 , 62
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.392: Finger status (picture number, mean) : 1 , 68
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.392: Finger status (picture number, mean) : 2 , 71
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.393: Finger status (picture number, mean) : 3 , 73
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.393: Finger status (picture number, mean) : 4 , 77
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.393: Image device reported finger status: on
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.393: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.393: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.393: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.393: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.393: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.393: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.394: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.394: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.394: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.395: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.395: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.395: Finger status (picture number, mean) : 0 , 79
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.395: Finger status (picture number, mean) : 1 , 79
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.395: Finger status (picture number, mean) : 2 , 82
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.395: Finger status (picture number, mean) : 3 , 84
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.395: Finger status (picture number, mean) : 4 , 85
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.395: Image device reported finger status: on
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.395: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.395: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.395: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.395: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.395: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.396: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.396: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.396: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.396: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.397: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.397: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.397: Finger status (picture number, mean) : 0 , 88
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.397: Finger status (picture number, mean) : 1 , 89
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.397: Finger status (picture number, mean) : 2 , 90
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.397: Finger status (picture number, mean) : 3 , 92
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.397: Finger status (picture number, mean) : 4 , 92
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.397: Image device reported finger status: on
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.397: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.397: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.397: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.397: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.397: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.398: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.398: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.398: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.399: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.399: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.399: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.399: Finger status (picture number, mean) : 0 , 93
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.399: Finger status (picture number, mean) : 1 , 94
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.399: Finger status (picture number, mean) : 2 , 95
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.399: Finger status (picture number, mean) : 3 , 96
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.399: Finger status (picture number, mean) : 4 , 97
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.399: Image device reported finger status: on
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.399: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.399: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.399: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.400: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.400: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.400: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.400: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.401: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.401: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.401: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.401: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.402: Finger status (picture number, mean) : 0 , 97
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.402: Finger status (picture number, mean) : 1 , 95
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.402: Finger status (picture number, mean) : 2 , 95
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.402: Finger status (picture number, mean) : 3 , 96
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.402: Finger status (picture number, mean) : 4 , 97
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.402: Image device reported finger status: on
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.402: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.402: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.402: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.402: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.402: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.402: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.403: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.403: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.403: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.403: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.403: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.404: Finger status (picture number, mean) : 0 , 96
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.404: Finger status (picture number, mean) : 1 , 97
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.404: Finger status (picture number, mean) : 2 , 98
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.404: Finger status (picture number, mean) : 3 , 98
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.404: Finger status (picture number, mean) : 4 , 98
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.404: Image device reported finger status: on
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.404: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.404: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.404: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.404: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.404: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.405: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.405: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.405: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.405: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.406: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.406: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.406: Finger status (picture number, mean) : 0 , 98
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.406: Finger status (picture number, mean) : 1 , 99
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.406: Finger status (picture number, mean) : 2 , 100
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.406: Finger status (picture number, mean) : 3 , 99
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.406: Finger status (picture number, mean) : 4 , 97
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.406: Image device reported finger status: on
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.406: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.406: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.406: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.406: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.406: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.407: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.407: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.407: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.408: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.408: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.408: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.408: Finger status (picture number, mean) : 0 , 98
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.408: Finger status (picture number, mean) : 1 , 98
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.408: Finger status (picture number, mean) : 2 , 98
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.408: Finger status (picture number, mean) : 3 , 95
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.408: Finger status (picture number, mean) : 4 , 91
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.408: Image device reported finger status: on
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.408: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.408: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.408: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.408: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.409: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.409: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.409: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.410: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.410: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.410: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.410: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.410: Finger status (picture number, mean) : 0 , 88
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.410: Finger status (picture number, mean) : 1 , 88
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.410: Finger status (picture number, mean) : 2 , 88
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.410: Finger status (picture number, mean) : 3 , 87
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.410: Finger status (picture number, mean) : 4 , 89
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.410: Image device reported finger status: on
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.410: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.410: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.410: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.411: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.411: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.411: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.411: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.412: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.412: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.412: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.412: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.413: Finger status (picture number, mean) : 0 , 88
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.413: Finger status (picture number, mean) : 1 , 89
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.413: Finger status (picture number, mean) : 2 , 90
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.413: Finger status (picture number, mean) : 3 , 91
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.413: Finger status (picture number, mean) : 4 , 89
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.413: Image device reported finger status: on
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.413: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.413: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.413: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.413: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.413: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.414: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.414: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.414: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.414: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.415: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.415: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.415: Finger status (picture number, mean) : 0 , 90
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.415: Finger status (picture number, mean) : 1 , 89
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.415: Finger status (picture number, mean) : 2 , 85
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.415: Finger status (picture number, mean) : 3 , 75
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.415: Finger status (picture number, mean) : 4 , 46
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.415: Image device reported finger status: on
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.415: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.415: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.415: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.415: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.415: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.416: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.416: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.416: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.417: [egis0570] SM_STATES_NUM entering state 2
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.417: [egis0570] SM_STATES_NUM entering state 3
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.417: [egis0570] SM_STATES_NUM entering state 4
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.417: Finger status (picture number, mean) : 0 , 17
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.417: Finger status (picture number, mean) : 1 , 14
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.417: Finger status (picture number, mean) : 2 , 15
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.417: Finger status (picture number, mean) : 3 , 15
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.417: Finger status (picture number, mean) : 4 , 15
205s (process:2650): libfprint-assembling-DEBUG: 05:03:36.477: calc delta completed in 0.059293 secs
205s (process:2650): libfprint-assembling-DEBUG: 05:03:36.536: calc delta completed in 0.059031 secs
205s (process:2650): libfprint-assembling-DEBUG: 05:03:36.536: errors: 10243 rev: 29954
205s (process:2650): libfprint-assembling-DEBUG: 05:03:36.595: calc delta completed in 0.058986 secs
205s (process:2650): libfprint-assembling-DEBUG: 05:03:36.595: height is 292
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.597: Image device captured an image
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.597: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
205s (process:2650): libfprint-device-DEBUG: 05:03:36.597: Device reported finger status change: FP_FINGER_STATUS_PRESENT
205s (process:2650): libfprint-device-DEBUG: 05:03:36.597: Device reported finger status change: FP_FINGER_STATUS_NONE
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.597: Image device reported finger status: off
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.597: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.597: Deactivating image device
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.597: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.597: [egis0570] SM_STATES_NUM entering state 5
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.597: [egis0570] SM_STATES_NUM entering state 1
205s (process:2650): libfprint-egis0570-DEBUG: 05:03:36.597: deactivating, marking completed
205s (process:2650): libfprint-SSM-DEBUG: 05:03:36.597: [egis0570] SM_STATES_NUM completed successfully
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.597: Image device deactivation completed
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.597: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
205s (process:2650): libfprint-image-DEBUG: 05:03:36.659: Minutiae scan completed in 0.061480 secs
205s (process:2650): libfprint-device-DEBUG: 05:03:36.659: Device reported capture completion
205s (process:2650): libfprint-device-DEBUG: 05:03:36.659: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
205s (process:2650): libfprint-device-DEBUG: 05:03:36.659: Updated temperature model after 0.27 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
205s (process:2650): libfprint-image_device-DEBUG: 05:03:36.659: Image device close completed
205s (process:2650): libfprint-device-DEBUG: 05:03:36.659: Device reported close completion
205s (process:2650): libfprint-device-DEBUG: 05:03:36.659: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
205s (process:2650): libfprint-device-DEBUG: 05:03:36.659: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
205s ** (umockdev-run:2646): DEBUG: 05:03:36.909: umockdev.vala:154: Removing test bed /tmp/umockdev.IN2D22
205s (umockdev-run:2646): GLib-DEBUG: 05:03:36.912: unsetenv() is not thread-safe and should not be used after threads are created
205s Comparing PNGs /tmp/libfprint-umockdev-test-5l2zayy6/capture.png and /usr/share/installed-tests/libfprint-2/egis0570/capture.png
206s PASS: libfprint-2/driver-egis0570.test
206s Running test: libfprint-2/driver-egismoc-0587.test
206s ** (umockdev-run:2659): DEBUG: 05:03:36.996: umockdev.vala:127: Created udev test bed /tmp/umockdev.GWP812
206s ** (umockdev-run:2659): DEBUG: 05:03:36.996: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3/3-5
206s ** (umockdev-run:2659): DEBUG: 05:03:36.998: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3/3-5 (subsystem usb)
206s ** (umockdev-run:2659): DEBUG: 05:03:36.999: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.GWP812/dev/bus/usb/003/009
206s ** (umockdev-run:2659): DEBUG: 05:03:36.999: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0/usb3
206s ** (umockdev-run:2659): DEBUG: 05:03:37.000: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0/usb3 (subsystem usb)
206s ** (umockdev-run:2659): DEBUG: 05:03:37.001: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.GWP812/dev/bus/usb/003/001
206s ** (umockdev-run:2659): DEBUG: 05:03:37.001: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:14.0
206s ** (umockdev-run:2659): DEBUG: 05:03:37.002: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:14.0 (subsystem pci)
206s (process:2663): libfprint-context-DEBUG: 05:03:37.059: Initializing FpContext (libfprint version 1.94.9+tod1)
206s (process:2663): libfprint-tod-DEBUG: 05:03:37.059: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.060: 83808911: ../libfprint/drivers/egismoc/egismoc.c:1597
206s (process:2663): libfprint-context-DEBUG: 05:03:37.060: No driver found for USB device 1D6B:0002
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.060: egismoc_probe enter --> 
206s (process:2663): libfprint-device-DEBUG: 05:03:37.061: Device reported probe completion
206s (process:2663): libfprint-device-DEBUG: 05:03:37.061: Completing action FPI_DEVICE_ACTION_PROBE in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.061: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.061: Opening device
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.062: [egismoc] DEV_INIT_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.062: [egismoc] DEV_INIT_STATES entering state 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.062: [egismoc] DEV_INIT_STATES entering state 2
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.062: [egismoc] DEV_INIT_STATES entering state 3
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.063: [egismoc] DEV_INIT_STATES entering state 4
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.063: [egismoc] DEV_INIT_STATES entering state 5
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.063: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.063: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.063: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.063: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.063: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.063: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.063: Firmware version callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.063: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.063: Device firmware version is 9050.6.4.67
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.063: [egismoc] DEV_INIT_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.063: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.063: Device reported open completion
206s (process:2663): libfprint-device-DEBUG: 05:03:37.063: Completing action FPI_DEVICE_ACTION_OPEN in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.063: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.064: List
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.064: [egismoc] LIST_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.064: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.064: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.064: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.064: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.064: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.064: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.064: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.064: Device fingerprint 1: FP1-00000000-2-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.064: Number of currently enrolled fingerprints on the device is 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.064: [egismoc] LIST_STATES entering state 1
206s (process:2663): libfprint-device-DEBUG: 05:03:37.064: Device reported listing completion
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.064: [egismoc] LIST_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.064: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.064: Completing action FPI_DEVICE_ACTION_LIST in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.064: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.064: Clear storage
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.064: [egismoc] DELETE_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.064: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.064: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.064: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.065: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.065: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.065: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.065: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.065: Device fingerprint 1: FP1-00000000-2-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.065: Number of currently enrolled fingerprints on the device is 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.065: [egismoc] DELETE_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.065: Get delete command
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.065: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.065: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.065: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.065: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.065: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.065: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.065: Delete callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.065: Response prefix valid: yes
206s (process:2663): libfprint-device-DEBUG: 05:03:37.065: Device reported deletion completion
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.065: [egismoc] DELETE_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.065: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.065: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.066: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.066: List
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.066: [egismoc] LIST_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.066: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.066: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.066: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.066: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.066: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.066: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.066: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.066: Number of currently enrolled fingerprints on the device is 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.066: [egismoc] LIST_STATES entering state 1
206s (process:2663): libfprint-device-DEBUG: 05:03:37.066: Device reported listing completion
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.066: [egismoc] LIST_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.066: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.066: Completing action FPI_DEVICE_ACTION_LIST in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.066: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
206s (process:2663): libfprint-device-DEBUG: 05:03:37.066: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.066: Enroll
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.066: [egismoc] ENROLL_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.066: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.066: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.066: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.067: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.067: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.067: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.067: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.067: Number of currently enrolled fingerprints on the device is 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.067: [egismoc] ENROLL_STATES entering state 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.067: [egismoc] ENROLL_STATES entering state 2
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.067: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.067: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.067: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.067: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.068: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.068: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.068: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.068: [egismoc] ENROLL_STATES entering state 3
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.068: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.068: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.068: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.068: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.068: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.068: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.068: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.068: [egismoc] ENROLL_STATES entering state 4
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.068: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.068: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.068: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.068: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.068: [egismoc] ENROLL_STATES entering state 5
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.068: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.068: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.068: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.069: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.069: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.069: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.069: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.069: [egismoc] ENROLL_STATES entering state 6
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.069: Get check command
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.069: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.069: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.069: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.069: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.069: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.069: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.069: Enroll check callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.069: Response suffix valid: yes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.069: [egismoc] ENROLL_STATES entering state 7
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.069: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.069: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.069: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.070: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.070: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.070: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.070: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.070: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.070: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.070: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.070: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.070: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.070: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.070: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.070: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.070: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.070: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.070: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.070: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.071: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.071: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.071: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.071: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.071: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.071: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.071: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.071: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.071: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.071: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.071: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.071: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.071: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.071: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.072: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.072: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.072: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.072: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.072: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.072: Partial capture successful. Please touch the sensor again (1/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.072: Device reported enroll progress, reported 1 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.072: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.072: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.072: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.072: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.072: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.072: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.072: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.072: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.072: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.072: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.072: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.072: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.073: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.073: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.073: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.073: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.073: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.073: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.073: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.073: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.073: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.073: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.073: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.073: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.073: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.073: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.074: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.074: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.074: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.074: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.074: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.074: Partial capture successful. Please touch the sensor again (2/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.074: Device reported enroll progress, reported 2 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.074: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.074: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.074: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.074: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.074: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.074: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.074: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.074: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.074: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.074: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.074: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.074: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.075: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.075: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.075: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.075: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.075: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.075: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.075: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.075: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.075: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.075: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.075: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.075: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.075: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.075: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.076: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.076: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.076: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.076: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.076: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.076: Partial capture successful. Please touch the sensor again (3/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.076: Device reported enroll progress, reported 3 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.076: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.076: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.076: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.076: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.076: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.076: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.076: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.076: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.076: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.076: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.076: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.076: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.076: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.077: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.077: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.077: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.077: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.077: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.077: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.077: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.077: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.077: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.077: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.077: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.077: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.077: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.077: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.077: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.078: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.078: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.078: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.078: Partial capture successful. Please touch the sensor again (4/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.078: Device reported enroll progress, reported 4 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.078: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.078: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.078: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.078: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.078: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.078: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.078: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.078: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.078: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.078: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.078: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.078: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.078: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.079: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.079: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.079: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.079: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.079: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.079: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.079: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.079: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.079: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.079: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.079: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.079: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.079: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.079: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.079: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.079: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.079: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.079: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.079: Partial capture successful. Please touch the sensor again (5/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.079: Device reported enroll progress, reported 5 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.079: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.079: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.079: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.079: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.080: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.080: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.080: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.080: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.080: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.080: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.080: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.080: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.080: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.080: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.080: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.080: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.080: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.080: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.080: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.081: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.081: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.081: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.081: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.081: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.081: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.081: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.081: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.081: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.081: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.081: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.081: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.081: Partial capture successful. Please touch the sensor again (6/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.081: Device reported enroll progress, reported 6 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.081: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.081: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.081: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.081: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.081: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.082: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.082: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.082: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.082: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.082: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.082: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.082: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.082: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.082: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.082: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.082: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.082: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.082: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.082: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.082: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.082: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.082: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.082: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.082: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.082: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.083: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.083: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.083: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.083: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.083: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.083: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.083: Partial capture successful. Please touch the sensor again (7/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.083: Device reported enroll progress, reported 7 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.083: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.083: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.083: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.083: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.083: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.083: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.083: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.083: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.083: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.083: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.083: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.083: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.084: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.084: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.084: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.084: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.084: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.084: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.084: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.084: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.084: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.084: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.084: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.084: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.084: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.085: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.085: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.085: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.085: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.085: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.085: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.085: Partial capture successful. Please touch the sensor again (8/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.085: Device reported enroll progress, reported 8 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.085: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.085: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.085: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.085: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.085: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.085: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.085: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.085: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.085: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.085: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.085: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.085: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.086: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.086: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.086: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.086: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.086: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.086: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.086: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.086: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.086: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.086: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.086: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.086: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.086: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.086: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.087: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.087: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.087: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.087: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.087: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.087: Partial capture successful. Please touch the sensor again (9/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.087: Device reported enroll progress, reported 9 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.087: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.087: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.087: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.087: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.087: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.087: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.087: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.087: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.087: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.087: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.087: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.087: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.087: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.088: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.088: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.088: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.088: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.088: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.088: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.088: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.088: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.088: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.088: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.088: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.088: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.088: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.089: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.089: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.089: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.089: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.089: Response suffix valid: NO
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.089: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.089: Response suffix valid: yes
206s (process:2663): libfprint-device-DEBUG: 05:03:37.089: Device reported enroll progress, reported 9 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.089: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.089: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.089: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.089: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.089: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.089: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.089: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.089: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.089: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.089: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.089: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.089: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.089: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.090: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.090: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.090: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.090: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.090: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.090: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.090: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.090: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.090: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.090: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.090: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.090: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.090: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.090: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.090: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.090: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.090: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.090: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.090: Partial capture successful. Please touch the sensor again (10/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.090: Device reported enroll progress, reported 10 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.091: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.091: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.091: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.091: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.091: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.091: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.091: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.091: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.091: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.091: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.091: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.091: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.091: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.091: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.092: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.092: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.092: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.092: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.092: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.092: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.092: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.092: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.092: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.092: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.092: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.092: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.092: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.092: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.092: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.092: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.092: Response suffix valid: NO
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.092: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.092: Response suffix valid: yes
206s (process:2663): libfprint-device-DEBUG: 05:03:37.092: Device reported enroll progress, reported 10 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.092: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.092: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.092: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.092: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.093: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.093: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.093: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.093: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.093: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.093: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.093: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.093: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.093: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.094: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.094: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.094: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.094: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.094: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.094: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.094: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.094: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.094: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.094: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.094: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.094: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.094: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.095: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.095: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.095: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.095: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.095: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.095: Partial capture successful. Please touch the sensor again (11/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.095: Device reported enroll progress, reported 11 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.095: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.095: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.095: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.095: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.095: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.095: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.095: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.095: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.095: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.095: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.095: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.095: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.095: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.096: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.096: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.096: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.096: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.096: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.096: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.096: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.096: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.096: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.096: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.096: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.096: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.096: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.096: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.096: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.096: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.096: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.096: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.096: Partial capture successful. Please touch the sensor again (12/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.096: Device reported enroll progress, reported 12 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.096: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.096: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.096: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.096: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.097: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.097: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.097: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.097: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.097: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.097: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.097: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.097: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.097: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.097: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.097: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.097: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.097: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.097: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.097: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.098: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.098: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.098: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.098: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.098: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.098: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.098: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.098: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.098: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.098: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.098: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.098: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.098: Partial capture successful. Please touch the sensor again (13/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.098: Device reported enroll progress, reported 13 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.098: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.098: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.098: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.098: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.098: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.099: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.099: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.099: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.099: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.099: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.099: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.099: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.099: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.099: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.099: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.099: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.099: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.099: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.099: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.099: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.100: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.100: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.100: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.100: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.100: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.100: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.100: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.100: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.100: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.100: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.100: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.100: Partial capture successful. Please touch the sensor again (14/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.100: Device reported enroll progress, reported 14 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.100: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.100: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.100: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.100: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.100: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.101: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.101: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.101: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.101: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.101: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.101: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.101: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.101: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.101: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.101: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.101: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.101: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.101: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.101: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.101: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.101: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.101: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.101: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.101: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.101: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.102: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.102: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.102: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.102: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.102: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.102: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.102: Partial capture successful. Please touch the sensor again (15/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.102: Device reported enroll progress, reported 15 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.102: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.102: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.102: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.102: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.102: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.102: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.102: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.102: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.102: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.102: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.102: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.102: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.103: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.103: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.103: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.103: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.103: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.103: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.103: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.103: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.103: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.103: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.103: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.103: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.103: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.104: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.104: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.104: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.104: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.104: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.104: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.104: Partial capture successful. Please touch the sensor again (16/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.104: Device reported enroll progress, reported 16 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.104: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.104: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.104: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.104: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.104: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.105: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.105: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.105: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.105: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.105: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.105: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.105: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.105: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.105: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.105: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.105: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.105: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.105: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.105: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.105: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.105: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.105: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.105: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.105: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.105: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.106: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.106: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.106: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.106: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.106: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.106: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.106: Partial capture successful. Please touch the sensor again (17/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.106: Device reported enroll progress, reported 17 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.106: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.106: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.106: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.106: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.106: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.106: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.107: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.107: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.107: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.107: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.107: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.107: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.107: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.107: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.107: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.107: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.107: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.107: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.107: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.107: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.107: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.107: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.107: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.107: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.107: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.108: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.108: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.108: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.108: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.108: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.108: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.108: Partial capture successful. Please touch the sensor again (18/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.108: Device reported enroll progress, reported 18 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.108: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.108: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.108: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.108: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.108: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.108: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.108: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.108: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.108: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.109: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.109: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.109: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.109: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.109: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.109: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.109: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.109: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.109: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.109: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.109: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.109: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.109: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.109: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.109: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.109: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.109: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.110: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.110: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.110: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.110: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.110: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.110: Partial capture successful. Please touch the sensor again (19/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.110: Device reported enroll progress, reported 19 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.110: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.110: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.110: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.110: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.110: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.110: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.110: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.110: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.110: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.110: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.110: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.110: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.111: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.111: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.111: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.111: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.111: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.111: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.111: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.111: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.111: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.111: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.111: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.111: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.111: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.111: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.112: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.112: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.112: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.112: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.112: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.112: Partial capture successful. Please touch the sensor again (20/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.112: Device reported enroll progress, reported 20 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.112: [egismoc] ENROLL_STATES entering state 12
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.112: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.112: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.112: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.112: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.112: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.112: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.112: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.112: [egismoc] ENROLL_STATES entering state 13
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.112: New fingerprint ID: FP1-00000000-2-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.112: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.112: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.112: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.112: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.113: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.113: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.113: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.113: [egismoc] ENROLL_STATES entering state 14
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.113: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.113: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.113: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.113: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.113: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.113: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.113: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.113: [egismoc] ENROLL_STATES entering state 15
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.113: Enrollment was successful!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.113: Device reported enroll completion
206s (process:2663): libfprint-device-DEBUG: 05:03:37.113: Device reported finger status change: FP_FINGER_STATUS_NONE
206s (process:2663): libfprint-device-DEBUG: 05:03:37.113: Print for finger FP_FINGER_LEFT_INDEX enrolled
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.113: [egismoc] ENROLL_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.113: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.113: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.113: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.113: List
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.113: [egismoc] LIST_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.113: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.113: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.113: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.114: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.114: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.114: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.114: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.114: Device fingerprint 1: FP1-00000000-2-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.114: Number of currently enrolled fingerprints on the device is 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.114: [egismoc] LIST_STATES entering state 1
206s (process:2663): libfprint-device-DEBUG: 05:03:37.114: Device reported listing completion
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.114: [egismoc] LIST_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.114: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.114: Completing action FPI_DEVICE_ACTION_LIST in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.114: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-device-DEBUG: 05:03:37.114: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.114: Identify or Verify
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.114: [egismoc] IDENTIFY_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.114: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.114: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.114: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.114: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.114: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.114: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.115: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.115: Device fingerprint 1: FP1-00000000-2-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.115: Number of currently enrolled fingerprints on the device is 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.115: [egismoc] IDENTIFY_STATES entering state 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.115: [egismoc] IDENTIFY_STATES entering state 2
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.115: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.115: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.115: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.115: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.115: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.115: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.115: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.115: [egismoc] IDENTIFY_STATES entering state 3
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.115: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.115: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.115: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.115: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.116: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.116: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.116: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.116: [egismoc] IDENTIFY_STATES entering state 4
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.116: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.116: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.116: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.116: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.116: [egismoc] IDENTIFY_STATES entering state 5
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.116: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.116: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.116: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.116: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.116: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.116: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.116: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.116: [egismoc] IDENTIFY_STATES entering state 6
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.116: Get check command
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.116: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.116: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.116: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.117: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.117: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.117: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.117: Identify check callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.117: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.117: Identify successful for: FP1-00000000-2-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.117: Verifying against: FP1-00000000-2-00000000-nobody
206s (process:2663): libfprint-device-DEBUG: 05:03:37.117: Device reported verify result
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.117: [egismoc] IDENTIFY_STATES entering state 7
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.117: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.117: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.117: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.117: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.117: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.117: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.117: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.117: [egismoc] IDENTIFY_STATES entering state 8
206s (process:2663): libfprint-device-DEBUG: 05:03:37.117: Device reported verify completion
206s (process:2663): libfprint-device-DEBUG: 05:03:37.117: Device reported finger status change: FP_FINGER_STATUS_NONE
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.117: [egismoc] IDENTIFY_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.117: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.117: Completing action FPI_DEVICE_ACTION_VERIFY in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.117: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-device-DEBUG: 05:03:37.118: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.118: Identify or Verify
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.118: [egismoc] IDENTIFY_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.118: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.118: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.118: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.118: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.118: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.118: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.118: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.118: Device fingerprint 1: FP1-00000000-2-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.118: Number of currently enrolled fingerprints on the device is 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.118: [egismoc] IDENTIFY_STATES entering state 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.118: [egismoc] IDENTIFY_STATES entering state 2
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.118: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.118: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.118: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.119: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.119: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.119: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.119: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.119: [egismoc] IDENTIFY_STATES entering state 3
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.119: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.119: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.119: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.119: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.119: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.120: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.120: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.120: [egismoc] IDENTIFY_STATES entering state 4
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.120: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.120: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.120: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.120: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.120: [egismoc] IDENTIFY_STATES entering state 5
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.120: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.120: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.120: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.120: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.120: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.120: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.120: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.120: [egismoc] IDENTIFY_STATES entering state 6
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.120: Get check command
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.120: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.120: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.120: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.121: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.121: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.121: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.121: Identify check callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.121: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.121: Identify successful for: FP1-00000000-2-00000000-nobody
206s (process:2663): libfprint-device-DEBUG: 05:03:37.121: Device reported identify result
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.121: [egismoc] IDENTIFY_STATES entering state 7
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.121: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.121: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.121: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.121: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.121: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.121: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.121: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.121: [egismoc] IDENTIFY_STATES entering state 8
206s (process:2663): libfprint-device-DEBUG: 05:03:37.121: Device reported identify completion
206s (process:2663): libfprint-device-DEBUG: 05:03:37.121: Device reported finger status change: FP_FINGER_STATUS_NONE
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.121: [egismoc] IDENTIFY_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.121: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.121: Completing action FPI_DEVICE_ACTION_IDENTIFY in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.121: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-device-DEBUG: 05:03:37.122: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.122: Enroll
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.122: [egismoc] ENROLL_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.122: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.122: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.122: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.122: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.122: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.122: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.122: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.122: Device fingerprint 1: FP1-00000000-2-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.122: Number of currently enrolled fingerprints on the device is 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.122: [egismoc] ENROLL_STATES entering state 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.122: [egismoc] ENROLL_STATES entering state 2
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.122: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.122: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.122: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.123: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.123: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.123: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.123: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.123: [egismoc] ENROLL_STATES entering state 3
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.123: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.123: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.123: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.123: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.124: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.124: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.124: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.124: [egismoc] ENROLL_STATES entering state 4
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.124: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.124: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.124: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.124: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.124: [egismoc] ENROLL_STATES entering state 5
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.124: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.124: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.124: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.124: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.124: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.124: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.124: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.124: [egismoc] ENROLL_STATES entering state 6
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.124: Get check command
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.124: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.124: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.124: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.125: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.125: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.125: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.125: Enroll check callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.125: Response suffix valid: NO
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.125: [egismoc] SSM ENROLL_STATES failed in state 6 with error: This finger has already enrolled, please try a different finger
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.125: [egismoc] ENROLL_STATES completed with error: This finger has already enrolled, please try a different finger
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.125: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.125: Device reported generic error (This finger has already enrolled, please try a different finger) during action; action was: FPI_DEVICE_ACTION_ENROLL
206s (process:2663): libfprint-device-DEBUG: 05:03:37.125: Device reported enroll completion
206s (process:2663): libfprint-device-DEBUG: 05:03:37.125: Device reported finger status change: FP_FINGER_STATUS_NONE
206s (process:2663): libfprint-device-DEBUG: 05:03:37.125: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.125: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.125: List
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.125: [egismoc] LIST_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.125: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.125: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.125: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.125: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.125: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.125: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.126: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.126: Device fingerprint 1: FP1-00000000-2-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.126: Number of currently enrolled fingerprints on the device is 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.126: [egismoc] LIST_STATES entering state 1
206s (process:2663): libfprint-device-DEBUG: 05:03:37.126: Device reported listing completion
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.126: [egismoc] LIST_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.126: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.126: Completing action FPI_DEVICE_ACTION_LIST in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.126: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-device-DEBUG: 05:03:37.126: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.126: Enroll
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.126: [egismoc] ENROLL_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.126: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.126: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.126: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.126: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.126: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.126: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.126: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.126: Device fingerprint 1: FP1-00000000-2-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.126: Number of currently enrolled fingerprints on the device is 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.126: [egismoc] ENROLL_STATES entering state 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.126: [egismoc] ENROLL_STATES entering state 2
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.126: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.126: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.126: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.127: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.127: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.127: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.127: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.127: [egismoc] ENROLL_STATES entering state 3
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.127: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.127: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.127: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.127: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.127: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.127: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.127: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.127: [egismoc] ENROLL_STATES entering state 4
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.127: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.127: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.128: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.128: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.128: [egismoc] ENROLL_STATES entering state 5
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.128: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.128: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.128: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.128: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.128: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.128: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.128: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.128: [egismoc] ENROLL_STATES entering state 6
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.128: Get check command
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.128: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.128: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.128: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.128: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.129: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.129: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.129: Enroll check callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.129: Response suffix valid: yes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.129: [egismoc] ENROLL_STATES entering state 7
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.129: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.129: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.129: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.129: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.129: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.129: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.129: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.129: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.129: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.129: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.129: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.129: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.130: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.130: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.130: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.130: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.130: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.130: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.130: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.130: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.130: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.130: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.130: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.130: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.130: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.130: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.130: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.130: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.130: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.130: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.130: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.130: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.131: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.131: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.131: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.131: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.131: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.131: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.131: Partial capture successful. Please touch the sensor again (1/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.131: Device reported enroll progress, reported 1 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.131: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.131: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.131: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.131: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.131: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.131: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.131: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.131: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.131: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.131: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.131: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.131: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.132: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.132: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.132: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.132: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.132: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.132: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.132: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.132: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.132: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.132: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.132: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.132: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.132: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.132: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.133: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.133: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.133: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.133: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.133: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.133: Partial capture successful. Please touch the sensor again (2/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.133: Device reported enroll progress, reported 2 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.133: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.133: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.133: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.133: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.133: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.133: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.133: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.133: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.133: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.133: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.133: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.133: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.134: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.134: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.134: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.134: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.134: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.134: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.134: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.134: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.134: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.134: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.134: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.134: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.134: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.134: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.135: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.135: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.135: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.135: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.135: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.135: Partial capture successful. Please touch the sensor again (3/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.135: Device reported enroll progress, reported 3 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.135: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.135: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.135: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.135: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.135: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.135: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.135: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.135: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.135: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.135: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.135: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.135: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.136: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.136: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.136: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.136: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.136: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.136: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.136: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.136: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.136: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.136: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.136: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.136: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.136: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.136: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.137: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.137: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.137: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.137: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.137: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.137: Partial capture successful. Please touch the sensor again (4/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.137: Device reported enroll progress, reported 4 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.137: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.137: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.137: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.137: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.137: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.137: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.137: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.137: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.137: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.137: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.137: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.137: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.137: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.138: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.138: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.138: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.138: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.138: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.138: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.138: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.138: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.138: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.138: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.138: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.138: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.138: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.138: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.138: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.138: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.138: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.138: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.138: Partial capture successful. Please touch the sensor again (5/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.138: Device reported enroll progress, reported 5 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.138: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.138: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.138: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.138: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.139: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.139: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.139: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.139: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.139: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.139: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.139: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.139: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.139: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.139: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.139: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.139: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.139: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.139: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.139: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.140: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.140: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.140: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.140: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.140: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.140: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.140: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.140: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.140: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.140: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.140: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.140: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.140: Partial capture successful. Please touch the sensor again (6/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.140: Device reported enroll progress, reported 6 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.140: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.140: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.140: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.140: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.140: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.141: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.141: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.141: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.141: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.141: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.141: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.141: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.141: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.141: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.141: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.141: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.141: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.141: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.141: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.141: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.141: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.141: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.141: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.141: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.141: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.142: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.142: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.142: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.142: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.142: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.142: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.142: Partial capture successful. Please touch the sensor again (7/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.142: Device reported enroll progress, reported 7 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.142: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.142: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.142: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.142: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.142: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.142: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.142: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.142: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.142: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.142: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.142: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.142: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.143: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.143: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.143: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.143: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.143: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.143: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.143: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.143: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.143: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.143: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.143: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.143: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.143: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.143: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.144: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.144: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.144: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.144: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.144: Response suffix valid: NO
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.144: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.144: Response suffix valid: yes
206s (process:2663): libfprint-device-DEBUG: 05:03:37.144: Device reported enroll progress, reported 7 of 20 have been completed
206s listing - device should have prints
206s clear device storage
206s clear done
206s listing - device should be empty
206s enrolling
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 1, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 2, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 3, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 4, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 5, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 6, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 7, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 8, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 9, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 9, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 10, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 10, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 11, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 12, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 13, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 14, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 15, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 16, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 17, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 18, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 19, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 20, <FPrint.Print object at 0x3ffa710fd80 (FpPrint at 0x33699f0)>, None, None)
206s enroll done
206s listing - device should have 1 print
206s verifying
206s verify done
206s async identifying
206s indentification_done:  <FPrint.Print object at 0x3ffa7113340 (FpPrint at 0x3376a90)> <FPrint.Print object at 0x3ffa7113380 (FpPrint at 0x337a620)>
206s try to enroll duplicate
206s duplicate enroll attempt done
206s listing - device should still only have 1 print
206s enroll new finger
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 1, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 2, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 3, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 4, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 5, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 6, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 7, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>(process:2663): libfprint-SSM-DEBUG: 05:03:37.144: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.144: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.144: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.144: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.144: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.144: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.144: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.144: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.144: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.144: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.144: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.144: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.145: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.145: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.145: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.145: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.145: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.145: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.145: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.145: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.145: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.145: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.145: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.145: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.145: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.145: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.146: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.146: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.146: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.146: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.146: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.146: Partial capture successful. Please touch the sensor again (8/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.146: Device reported enroll progress, reported 8 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.146: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.146: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.146: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.146: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.146: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.146: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.146: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.146: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.146: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.146: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.146: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.146: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.146: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.147: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.147: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.147: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.147: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.147: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.147: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.147: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.147: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.147: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.147: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.147: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.147: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.147: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.147: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.147: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.147: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.147: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.147: Response suffix valid: NO
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.147: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.147: Response suffix valid: yes
206s (process:2663): libfprint-device-DEBUG: 05:03:37.147: Device reported enroll progress, reported 8 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.147: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.147: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.147: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.147: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.148: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.148: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.148: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.148: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.148: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.148: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.148: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.148: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.148: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.148: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.148: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.148: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.148: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.148: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.148: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.149: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.149: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.149: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.149: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.149: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.149: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.149: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.149: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.149: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.149: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.149: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.149: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.149: Partial capture successful. Please touch the sensor again (9/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.149: Device reported enroll progress, reported 9 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.149: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.149: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.149: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.149: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.149: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.150: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.150: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.150: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.150: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.150: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.150: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.150: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.150: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.150: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.150: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.150: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.150: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.150: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.150: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.150: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.150: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.150: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.150: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.150: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.150: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.151: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.151: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.151: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.151: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.151: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.151: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.151: Partial capture successful. Please touch the sensor again (10/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.151: Device reported enroll progress, reported 10 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.151: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.151: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.151: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.151: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.151: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.151: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.151: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.151: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.151: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.151: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.151: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.151: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.152: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.152: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.152: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.152: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.152: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.152: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.152: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.152: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.152: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.152: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.152: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.152: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.152: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.152: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.153: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.153: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.153: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.153: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.153: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.153: Partial capture successful. Please touch the sensor again (11/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.153: Device reported enroll progress, reported 11 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.153: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.153: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.153: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.153: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.153: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.153: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.153: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.153: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.153: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.153: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.153: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.153: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.154: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.154: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.154: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.154: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.154: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.154: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.154: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.154: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.154: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.154: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.154: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.154: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.154: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.154: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.155: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.155: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.155: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.155: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.155: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.155: Partial capture successful. Please touch the sensor again (12/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.155: Device reported enroll progress, reported 12 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.155: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.155: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.155: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.155: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.155: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.155: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.155: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.155: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.155: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.155: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.155: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.155: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.156: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.156: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.156: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.156: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.156: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.156: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.156: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.156: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.156: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.156: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.156: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.156: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.156: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.156: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.157: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.157: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.157: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.157: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.157: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.157: Partial capture successful. Please touch the sensor again (13/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.157: Device reported enroll progress, reported 13 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.157: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.157: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.157: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.157: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.157: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.157: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.157: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.157: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.157: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.157: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.157: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.157: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.157: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.158: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.158: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.158: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.158: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.158: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.158: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.158: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.158: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.158: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.158: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.158: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.158: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.158: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.158: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.158: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.158: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.158: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.158: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.158: Partial capture successful. Please touch the sensor again (14/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.158: Device reported enroll progress, reported 14 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.158: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.158: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.158: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.158: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.159: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.159: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.159: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.159: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.159: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.159: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.159: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.159: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.159: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.159: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.159: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.159: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.159: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.159: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.159: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.160: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.160: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.160: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.160: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.160: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.160: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.160: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.160: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.160: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.160: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.160: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.160: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.160: Partial capture successful. Please touch the sensor again (15/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.160: Device reported enroll progress, reported 15 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.160: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.160: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.160: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.160: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.160: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.161: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.161: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.161: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.161: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.161: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.161: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.161: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.161: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.161: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.161: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.161: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.161: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.161: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.161: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.161: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.161: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.161: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.161: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.161: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.161: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.162: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.162: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.162: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.162: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.162: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.162: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.162: Partial capture successful. Please touch the sensor again (16/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.162: Device reported enroll progress, reported 16 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.162: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.162: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.162: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.162: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.162: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.162: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.162: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.162: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.162: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.162: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.162: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.162: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.163: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.163: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.163: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.163: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.163: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.163: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.163: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.163: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.163: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.163: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.163: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.163: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.163: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.163: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.164: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.164: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.164: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.164: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.164: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.164: Partial capture successful. Please touch the sensor again (17/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.164: Device reported enroll progress, reported 17 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.164: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.164: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.164: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.164: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.164: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.164: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.164: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.164: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.164: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.164: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.164: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.164: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.164: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.165: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.165: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.165: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.165: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.165: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.165: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.165: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.165: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.165: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.165: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.165: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.165: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.165: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.165: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.165: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.165: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.165: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.166: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.166: Partial capture successful. Please touch the sensor again (18/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.166: Device reported enroll progress, reported 18 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.166: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.166: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.166: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.166: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.166: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.166: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.166: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.166: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.166: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.166: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.166: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.166: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.166: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.167: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.167: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.167: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.167: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.167: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.167: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.167: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.167: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.167: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.167: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.167: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.167: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.167: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.167: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.167: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.167: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.167: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.167: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.167: Partial capture successful. Please touch the sensor again (19/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.167: Device reported enroll progress, reported 19 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.167: [egismoc] ENROLL_STATES entering state 8
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.167: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.167: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.167: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.168: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.168: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.168: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.168: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.168: [egismoc] ENROLL_STATES entering state 9
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.168: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.168: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.168: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.168: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.168: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.168: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.168: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.168: [egismoc] ENROLL_STATES entering state 10
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.168: Wait for finger on sensor
206s (process:2663): libfprint-device-DEBUG: 05:03:37.168: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.169: Finger on sensor callback
206s (process:2663): libfprint-device-DEBUG: 05:03:37.169: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.169: [egismoc] ENROLL_STATES entering state 11
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.169: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.169: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.169: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.169: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.169: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.169: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.169: Read capture callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.169: Response prefix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.169: Response suffix valid: yes
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.169: Partial capture successful. Please touch the sensor again (20/20)
206s (process:2663): libfprint-device-DEBUG: 05:03:37.169: Device reported enroll progress, reported 20 of 20 have been completed
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.169: [egismoc] ENROLL_STATES entering state 12
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.169: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.169: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.169: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.169: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.170: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.170: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.170: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.170: [egismoc] ENROLL_STATES entering state 13
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.170: New fingerprint ID: FP1-00000000-7-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.170: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.170: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.170: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.170: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.170: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.170: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.170: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.170: [egismoc] ENROLL_STATES entering state 14
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.170: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.170: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.170: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.170: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.171: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: Task SSM next state callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.171: [egismoc] ENROLL_STATES entering state 15
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: Enrollment was successful!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.171: Device reported enroll completion
206s (process:2663): libfprint-device-DEBUG: 05:03:37.171: Device reported finger status change: FP_FINGER_STATUS_NONE
206s (process:2663): libfprint-device-DEBUG: 05:03:37.171: Print for finger FP_FINGER_RIGHT_INDEX enrolled
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.171: [egismoc] ENROLL_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.171: Completing action FPI_DEVICE_ACTION_ENROLL in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.171: Updated temperature model after 0.05 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: List
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.171: [egismoc] LIST_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.171: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.171: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.171: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: Device fingerprint 1: FP1-00000000-2-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: Device fingerprint 2: FP1-00000000-7-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: Number of currently enrolled fingerprints on the device is 2
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.171: [egismoc] LIST_STATES entering state 1
206s (process:2663): libfprint-device-DEBUG: 05:03:37.171: Device reported listing completion
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.171: [egismoc] LIST_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.171: Completing action FPI_DEVICE_ACTION_LIST in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.171: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: Delete
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.171: [egismoc] DELETE_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.171: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.171: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.172: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.172: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: Device fingerprint 1: FP1-00000000-2-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: Device fingerprint 2: FP1-00000000-7-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: Number of currently enrolled fingerprints on the device is 2
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.172: [egismoc] DELETE_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: Get delete command
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: Delete fingerprint FP1-00000000-2-00000000-nobody (FP1-00000000-2-00000000-nobody)
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.172: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.172: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.172: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: Delete callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: Response prefix valid: yes
206s (process:2663): libfprint-device-DEBUG: 05:03:37.172: Device reported deletion completion
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.172: [egismoc] DELETE_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.172: Completing action FPI_DEVICE_ACTION_DELETE in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.172: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: List
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.172: [egismoc] LIST_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.172: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.172: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.173: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.173: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.173: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.173: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.173: Device fingerprint 1: FP1-00000000-7-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.173: Number of currently enrolled fingerprints on the device is 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.173: [egismoc] LIST_STATES entering state 1
206s (process:2663): libfprint-device-DEBUG: 05:03:37.173: Device reported listing completion
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.173: [egismoc] LIST_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.173: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.173: Completing action FPI_DEVICE_ACTION_LIST in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.173: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.173: Clear storage
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.173: [egismoc] DELETE_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.173: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.173: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.173: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.173: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.174: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.174: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.174: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.174: Device fingerprint 1: FP1-00000000-7-00000000-nobody
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.174: Number of currently enrolled fingerprints on the device is 1
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.174: [egismoc] DELETE_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.174: Get delete command
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.174: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.174: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.174: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.174: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.174: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.174: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.174: Delete callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.174: Response prefix valid: yes
206s (process:2663): libfprint-device-DEBUG: 05:03:37.174: Device reported deletion completion
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.174: [egismoc] DELETE_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.174: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.174: Completing action FPI_DEVICE_ACTION_CLEAR_STORAGE in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.174: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.174: List
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.174: [egismoc] LIST_STATES entering state 0
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.174: Execute command and get response
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.174: Get check bytes
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.174: [egismoc] CMD_STATES entering state 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.174: [egismoc] CMD_STATES entering state 1
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.175: Command receive callback
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.175: [egismoc] CMD_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.175: List callback
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.175: Number of currently enrolled fingerprints on the device is 0
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.175: [egismoc] LIST_STATES entering state 1
206s (process:2663): libfprint-device-DEBUG: 05:03:37.175: Device reported listing completion
206s (process:2663): libfprint-SSM-DEBUG: 05:03:37.175: [egismoc] LIST_STATES completed successfully
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.175: Task SSM done
206s (process:2663): libfprint-device-DEBUG: 05:03:37.175: Completing action FPI_DEVICE_ACTION_LIST in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.175: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.175: Closing device
206s (process:2663): libfprint-egismoc-DEBUG: 05:03:37.175: Cancel
206s (process:2663): libfprint-device-DEBUG: 05:03:37.175: Device reported close completion
206s (process:2663): libfprint-device-DEBUG: 05:03:37.175: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
206s (process:2663): libfprint-device-DEBUG: 05:03:37.175: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s 
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 7, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 8, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 8, None, None, GLib.Error('The finger was not centered properly, please try again.', 'fp - device - retry - quark', 2))
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 9, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 10, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 11, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 12, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 13, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 14, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 15, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 16, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 17, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 18, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 19, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s finger status:  <flags FP_FINGER_STATUS_PRESENT of type FPrint.FingerStatusFlags>
206s enroll progress: (<__gi__.FpiDeviceEgisMoc object at 0x3ffa710e680 (FpiDeviceEgisMoc at 0x3373920)>, 20, <FPrint.Print object at 0x3ffa7113ac0 (FpPrint at 0x337cb40)>, None, None)
206s enroll new finger done
206s listing - device should have 2 prints
206s deleting first print
206s delete done
206s listing - device should only have second print
206s clear device storage
206s clear done
206s listing - device should be empty
206s ** (umockdev-run:2659): DEBUG: 05:03:37.185: umockdev.vala:154: Removing test bed /tmp/umockdev.GWP812
206s (umockdev-run:2659): GLib-DEBUG: 05:03:37.187: unsetenv() is not thread-safe and should not be used after threads are created
206s PASS: libfprint-2/driver-egismoc-0587.test
206s Running test: libfprint-2/driver-aes3500.test
206s ** (umockdev-run:2671): DEBUG: 05:03:37.217: umockdev.vala:127: Created udev test bed /tmp/umockdev.3LUD22
206s ** (umockdev-run:2671): DEBUG: 05:03:37.217: 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
206s ** (umockdev-run:2671): DEBUG: 05:03:37.219: 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)
206s ** (umockdev-run:2671): DEBUG: 05:03:37.220: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3LUD22/dev/bus/usb/003/004
206s ** (umockdev-run:2671): DEBUG: 05:03:37.220: 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
206s ** (umockdev-run:2671): DEBUG: 05:03:37.223: 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)
206s ** (umockdev-run:2671): DEBUG: 05:03:37.224: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3LUD22/dev/bus/usb/003/003
206s ** (umockdev-run:2671): DEBUG: 05:03:37.224: 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
206s ** (umockdev-run:2671): DEBUG: 05:03:37.226: 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)
206s ** (umockdev-run:2671): DEBUG: 05:03:37.227: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3LUD22/dev/bus/usb/003/002
206s ** (umockdev-run:2671): DEBUG: 05:03:37.227: 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
206s ** (umockdev-run:2671): DEBUG: 05:03:37.229: 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)
206s ** (umockdev-run:2671): DEBUG: 05:03:37.230: umockdev.vala:1538: create_node_for_device: creating file device /tmp/umockdev.3LUD22/dev/bus/usb/003/001
206s ** (umockdev-run:2671): DEBUG: 05:03:37.230: 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
206s ** (umockdev-run:2671): DEBUG: 05:03:37.231: 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)
206s ** (umockdev-run:2671): DEBUG: 05:03:37.232: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0
206s ** (umockdev-run:2671): DEBUG: 05:03:37.233: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0/0000:02:02.0 (subsystem pci)
206s ** (umockdev-run:2671): DEBUG: 05:03:37.234: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0/0000:01:00.0
206s ** (umockdev-run:2671): DEBUG: 05:03:37.235: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0/0000:01:00.0 (subsystem pci)
206s ** (umockdev-run:2671): DEBUG: 05:03:37.236: umockdev.vala:1414: parsing device description for /devices/pci0000:00/0000:00:1c.0
206s ** (umockdev-run:2671): DEBUG: 05:03:37.236: umockdev.vala:1492: creating device /devices/pci0000:00/0000:00:1c.0 (subsystem pci)
206s (umockdev-run:2671): GLib-GIO-DEBUG: 05:03:37.237: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
206s (process:2675): libfprint-context-DEBUG: 05:03:37.295: Initializing FpContext (libfprint version 1.94.9+tod1)
206s (process:2675): libfprint-tod-DEBUG: 05:03:37.295: Impossible to load the shared drivers dir Error opening directory “/usr/lib/s390x-linux-gnu/libfprint-2/tod-1”: No such file or directory
206s (process:2675): libfprint-context-DEBUG: 05:03:37.297: No driver found for USB device 2230:0006
206s (process:2675): libfprint-context-DEBUG: 05:03:37.297: No driver found for USB device 2230:0006
206s (process:2675): libfprint-context-DEBUG: 05:03:37.297: No driver found for USB device 1D6B:0002
206s (process:2675): libfprint-device-DEBUG: 05:03:37.297: Device reported probe completion
206s (process:2675): libfprint-device-DEBUG: 05:03:37.297: Completing action FPI_DEVICE_ACTION_PROBE in idle!
206s (process:2675): libfprint-device-DEBUG: 05:03:37.297: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.298: Image device open completed
206s (process:2675): libfprint-device-DEBUG: 05:03:37.298: Device reported open completion
206s (process:2675): libfprint-device-DEBUG: 05:03:37.298: Completing action FPI_DEVICE_ACTION_OPEN in idle!
206s (process:2675): libfprint-device-DEBUG: 05:03:37.298: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
206s (process:2675): libfprint-device-DEBUG: 05:03:37.298: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 1 -> 1, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_COLD
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.298: Activating image device
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.298: Image device internal state change from FPI_IMAGE_DEVICE_STATE_INACTIVE to FPI_IMAGE_DEVICE_STATE_ACTIVATING
206s (process:2675): libfprint-aeslib-DEBUG: 05:03:37.298: write 50 regs
206s (process:2675): libfprint-aeslib-DEBUG: 05:03:37.300: all registers written
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.300: Image device activation completed
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_ACTIVATING to FPI_IMAGE_DEVICE_STATE_IDLE
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.300: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON
206s (process:2675): libfprint-aeslib-DEBUG: 05:03:37.300: write 6 regs
206s (process:2675): libfprint-device-DEBUG: 05:03:37.301: Device reported finger status change: FP_FINGER_STATUS_NEEDED
206s (process:2675): libfprint-aeslib-DEBUG: 05:03:37.301: all registers written
206s (process:2675): libfprint-device-DEBUG: 05:03:37.301: Device reported finger status change: FP_FINGER_STATUS_NEEDED | FP_FINGER_STATUS_PRESENT
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.301: Image device reported finger status: on
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.301: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_ON to FPI_IMAGE_DEVICE_STATE_CAPTURE
206s (process:2675): libfprint-aes3k-DEBUG: 05:03:37.301: frame header byte e0
206s (process:2675): libfprint-aes3k-DEBUG: 05:03:37.301: frame header byte e1
206s (process:2675): libfprint-aes3k-DEBUG: 05:03:37.301: frame header byte e2
206s (process:2675): libfprint-aes3k-DEBUG: 05:03:37.301: frame header byte e3
206s (process:2675): libfprint-aes3k-DEBUG: 05:03:37.301: frame header byte e4
206s (process:2675): libfprint-aes3k-DEBUG: 05:03:37.301: frame header byte e5
206s (process:2675): libfprint-aes3k-DEBUG: 05:03:37.301: frame header byte e6
206s (process:2675): libfprint-aes3k-DEBUG: 05:03:37.302: frame header byte e7
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.302: Image device captured an image
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.302: Image device internal state change from FPI_IMAGE_DEVICE_STATE_CAPTURE to FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF
206s (process:2675): libfprint-device-DEBUG: 05:03:37.302: Device reported finger status change: FP_FINGER_STATUS_PRESENT
206s (process:2675): libfprint-device-DEBUG: 05:03:37.302: Device reported finger status change: FP_FINGER_STATUS_NONE
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.302: Image device reported finger status: off
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.302: Image device internal state change from FPI_IMAGE_DEVICE_STATE_AWAIT_FINGER_OFF to FPI_IMAGE_DEVICE_STATE_IDLE
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.302: Deactivating image device
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.302: Image device internal state change from FPI_IMAGE_DEVICE_STATE_IDLE to FPI_IMAGE_DEVICE_STATE_DEACTIVATING
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.302: Image device deactivation completed
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.302: Image device internal state change from FPI_IMAGE_DEVICE_STATE_DEACTIVATING to FPI_IMAGE_DEVICE_STATE_INACTIVE
206s (process:2675): libfprint-image-DEBUG: 05:03:37.331: Minutiae scan completed in 0.028271 secs
206s (process:2675): libfprint-device-DEBUG: 05:03:37.331: Device reported capture completion
206s (process:2675): libfprint-device-DEBUG: 05:03:37.331: Completing action FPI_DEVICE_ACTION_CAPTURE in idle!
206s (process:2675): libfprint-device-DEBUG: 05:03:37.331: Updated temperature model after 0.03 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_COLD -> FP_TEMPERATURE_WARM
206s (process:2675): libfprint-image_device-DEBUG: 05:03:37.331: Image device close completed
206s (process:2675): libfprint-device-DEBUG: 05:03:37.331: Device reported close completion
206s (process:2675): libfprint-device-DEBUG: 05:03:37.331: Completing action FPI_DEVICE_ACTION_CLOSE in idle!
206s (process:2675): libfprint-device-DEBUG: 05:03:37.331: Updated temperature model after 0.00 seconds, ratio 0.27 -> 0.27, active 0 -> 0, FP_TEMPERATURE_WARM -> FP_TEMPERATURE_WARM
206s ** (umockdev-run:2671): DEBUG: 05:03:37.422: umockdev.vala:154: Removing test bed /tmp/umockdev.3LUD22
206s (umockdev-run:2671): GLib-DEBUG: 05:03:37.427: unsetenv() is not thread-safe and should not be used after threads are created
206s Comparing PNGs /tmp/libfprint-umockdev-test-_pn2zj05/capture.png and /usr/share/installed-tests/libfprint-2/aes3500/capture.png
206s PASS: libfprint-2/driver-aes3500.test
206s SUMMARY: total=25; passed=24; skipped=0; failed=1; user=12.4s; system=2.0s; maxrss=46508
206s FAIL: libfprint-2/fpi-assembling.test (Child process killed by signal 6)
206s autopkgtest [05:03:37]: test installed-tests: -----------------------]
207s autopkgtest [05:03:38]: test installed-tests:  - - - - - - - - - - results - - - - - - - - - -
207s installed-tests      FAIL non-zero exit status 2
207s autopkgtest [05:03:38]: @@@@@@@@@@@@@@@@@@@@ summary
207s installed-tests      FAIL non-zero exit status 2
213s nova [W] Using flock in prodstack6-s390x
213s Creating nova instance adt-plucky-s390x-libfprint-20250222-050011-juju-7f2275-prod-proposed-migration-environment-15-7cb8cb3a-b960-4f3e-8c60-0f7bc457f82e from image adt/ubuntu-plucky-s390x-server-20250222.img (UUID ae633cda-0dee-481c-9805-d0ef3f3b5166)...
213s nova [W] Timed out waiting for 1b92b82d-89e3-490e-be6c-cd8e587693ab to get deleted.